How the chromium Git Repositories Page Is Organized

The page at chromium.googlesource.com is a plain alphabetical index of Git repositories hosted on the chromium host. Each entry is a repository name followed by a short description, and that description is what tells you whether the repo is the one you want. Repositories that have been relocated or renamed are still listed, with a "MOVED" note in the description pointing to the current location. The top of the page also carries links for Code Review, Generate Password, Revoke Passwords, and Sign in.

What the page contains

The heading is "Git repositories on chromium," and below it the repositories appear as a two-column list: Name and Description. There is no search box or category grouping described on the page, so navigation means scanning names and reading descriptions.

The top-of-page links serve account and review tasks rather than browsing:

• Code Review — entry point to the review tool used with these repositories
• Generate Password / Revoke Passwords — credential management for Git access
• Sign in — authentication

Reading the descriptions

Descriptions are short and often state the repo's origin or purpose. Two patterns are worth knowing:

Forks of AOSP. Many entries begin with aosp/ and describe themselves as a "ChromiumOS fork of" an android.googlesource.com path. For example, aosp/platform/system/core is described as the ChromiumOS fork of the Android platform system/core repo. These exist on the chromium host because ChromiumOS builds on Android-derived components.

Moved entries. A description containing "(MOVED)" means the repo no longer lives at that name. The note usually says where it went — merged into another path, renamed, or moved back to a different host. Examples from the page:

If you land on a MOVED entry, follow the path named in its description instead of cloning the old name.

Finding and cloning a repository

1. Identify the component. Decide which part of the codebase you need (for example, a Bluetooth module or a hardware interface). The name usually reflects the component path.
2. Scan the Name column for a match, then confirm against the Description. Prefer entries without "(MOVED)".
3. Check for a MOVED note before cloning. If present, switch to the location the description names.
4. Clone from the repository page. Selecting a repository name opens its page on the host, which provides the clone URL for that repo. Use the standard git clone <url> form with the URL shown there.
5. Verify by listing the cloned directory contents or checking git remote -v to confirm the origin matches the repo you intended.

A concrete case: if you need the ChromiumOS fork of Android's system/core, the entry aosp/platform/system/core is the right target, and its description confirms the fork relationship. If you instead pick aosp/platform/external/libchrome, the "(MOVED) to chromiumos/platform/libchrome" note tells you the clone would not give you the maintained code.

Common snags

• Cloning a stale name. The most likely mistake is picking a MOVED entry. The description is the only warning on the index page, so read it before copying a name.
• Confusing forks with upstream. An aosp/... entry on this host is a ChromiumOS fork, not the original Android repository. If you need upstream Android code, the description points to the android.googlesource.com path it was forked from.
• Assuming the list is complete or categorized. The page presents a flat name/description list; there is no indication of grouping by project, so long scans are expected.
• Credential steps. The Generate Password and Revoke Passwords links exist for managing Git access credentials, but the page itself does not describe the login requirements or terms of use for those tools — check the linked pages directly rather than assuming open access.