commit | c60b2b12cc5f7d2ed1701e863a6c6f3bb435534b | [log] [tgz] |
---|---|---|
author | Harry Souders <harrysouders@google.com> | Mon Jan 13 22:51:17 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jan 13 22:51:17 2025 |
tree | b9f929fca4e5044519a7fe099bbc087c41d75bf2 | |
parent | 81bfdf3e91f87bed205f66857360372bfd4740b8 [diff] |
Run Markdown linter over Merge Request process doc. This change does not introduce any actual changes. This is only to clean up the documentation before updating it in a future CL. Change-Id: I4aaa05881d6e9308c06d0d51d5ceb2e5e823d2c7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6170778 Commit-Queue: Harry Souders <harrysouders@google.com> Reviewed-by: Krishna Govind <govind@chromium.org> Cr-Commit-Position: refs/heads/main@{#1405770}
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.