Minor refactor of adding_to_third_party * Reduced the indentation of headings so that the TOC is more useful. * Changed 'README.chromium' to a H1 heading to make navigating from the TOC easier when looking for information on a specific field. * Reformatted [Update Mechanism](https://chromium.googlesource.com/chromium/src/+/800f641fc14175cdf1aa717679906f1ae561d35b/docs/adding_to_third_party.md?pli=1#update-mechanism) section to be more readable. Live Preview: https://chromium.googlesource.com/chromium/src/+/800f641fc14175cdf1aa717679906f1ae561d35b/docs/adding_to_third_party.md?pli=1#Autoroll Change-Id: I1339f5dbcc46cba56e18d1269648ac69b8a7c69d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6631790 Reviewed-by: Jiewei Qian <qjw@chromium.org> Commit-Queue: Jordan Brown <rop@google.com> Reviewed-by: Rachael Newitt <renewitt@google.com> Cr-Commit-Position: refs/heads/main@{#1472891}
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.