commit | 0cab2ccd2478b5d5a18ca569d0e7b99fec183a99 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Tue Feb 04 10:55:30 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Feb 04 10:55:30 2025 |
tree | 64496028b1af6afa823abc53b4641091e8dc620d | |
parent | ed6ec22a4ad6b7ea5bda190d13c1146daa1098ab [diff] |
Roll DevTools Frontend from 38e4503de3b3 to 697190003ea8 (1 revision) https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/38e4503de3b3..697190003ea8 2025-02-04 kimanh@chromium.org [doc] Add info on token files If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@rotations.google.com,liviurau@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Bug: chromium:357513556 Change-Id: I9f8a80042c83e9dd208c437578ba93debb93ff53 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6229339 Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1415472}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.