Clone this repo:

Branches

  1. bf3fe22 Generated files from "codesearch-gen-chromium-android" build 8708071557998121793, revision 2e71e412b473cc4634910e5cce0240bb441d746d by Automatic Generated Files Sync · 15 minutes ago main
  2. 1f09884 Generated files from "codesearch-gen-chromium-win" build 8708071557091314785, revision 2e71e412b473cc4634910e5cce0240bb441d746d by Automatic Generated Files Sync · 17 minutes ago
  3. 5cbd46d Generated files from "codesearch-gen-chromium-chromiumos" build 8708071557937466545, revision 2e71e412b473cc4634910e5cce0240bb441d746d by Automatic Generated Files Sync · 46 minutes ago
  4. 880c9c0 Generated files from "codesearch-gen-chromium-linux" build 8708071556926352369, revision 2e71e412b473cc4634910e5cce0240bb441d746d by Automatic Generated Files Sync · 73 minutes ago
  5. 3d0a81cf Generated files from "codesearch-gen-chromium-mac" build 8708071557863638945, revision 2e71e412b473cc4634910e5cce0240bb441d746d by Automatic Generated Files Sync · 79 minutes ago

What's this?

This git repository exists to allow the source files generated during a Chromium build to be indexed by code search.

You do not need to clone this repository, and it is not used in any way during a build.

How does it work?

A Codeserach builder (e.g. codesearch-gen-chromium-linux) regularly does a full build of Chromium, and afterwards pushes all the generated files (from the src/out/{out_dir}/gen directory) into this git repository.

The code search crawler indexes that gitlink repository following all the gitlinks inside, which eventually leads it here and allows it to index the generated code.