commit | b81291149f327c52c50fed63088b59a801c1fbf5 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Tue Feb 25 13:10:33 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Feb 25 13:10:33 2025 |
tree | 07f27a23a3c1a0233839f133bd64d588c7ce2a21 | |
parent | d604be9387533f07ad71e0b877dc485372f97cc5 [diff] |
Roll DevTools Frontend from 21a6a9dd8a66 to 7ea9140cf9fd (1 revision) https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/21a6a9dd8a66..7ea9140cf9fd 2025-02-25 liviurau@chromium.org Add siso dependencies 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: None Change-Id: Ib7ab82b7d15a5697ff6da61b9d18e9d8a9b14334 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6299723 Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1424461}
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.