Clone this repo:

Branches

  1. 1ecfba2 Generated files from "codesearch-gen-chromium-win" build 8682715688033570577, revision 670ea05f49a1c2a0b149856be285a4f31d11782c by Automatic Generated Files Sync · 4 hours ago main
  2. 22f4284 Generated files from "codesearch-gen-chromium-ios" build 8682715688033570641, revision 670ea05f49a1c2a0b149856be285a4f31d11782c by Automatic Generated Files Sync · 4 hours ago
  3. 6076220 Generated files from "codesearch-gen-chromium-android" build 8682715688033570705, revision 670ea05f49a1c2a0b149856be285a4f31d11782c by Automatic Generated Files Sync · 4 hours ago
  4. a089a46 Generated files from "codesearch-gen-chromium-chromiumos" build 8682715688033570689, revision 670ea05f49a1c2a0b149856be285a4f31d11782c by Automatic Generated Files Sync · 4 hours ago
  5. 4139d20 Generated files from "codesearch-gen-chromium-mac" build 8682715688033570609, revision 670ea05f49a1c2a0b149856be285a4f31d11782c by Automatic Generated Files Sync · 5 hours 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.