commit | 7864e54a5eec0b03a8e6195cd32c404ef5b56f03 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Wed Jan 29 16:15:18 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jan 29 16:15:18 2025 |
tree | 25de6d48eec43127e9b90e297bd4cb7d460388e3 | |
parent | bd092d6029054c5151cefe3cc5aa5e266f37faab [diff] |
Roll DevTools Frontend from 0846cc563b4d to c5e210744ce9 (1 revision) https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/0846cc563b4d..c5e210744ce9 2025-01-29 nvitkov@chromium.org [Lit] Enable no-unclosed-tag rule 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: Idff8b33b6e17f172caa0dcbeca9b6a264acf3a5a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6213424 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@{#1412940}
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.