Clone this repo:

Branches

  1. e72121fe4 Generated files from "codesearch-gen-chromium-win" build 8683349884183183905, revision 974d032a465edf08959681ed93a297ade2bd94c4 by Automatic Generated Files Sync · 4 hours ago main
  2. 32cd1ba Generated files from "codesearch-gen-chromium-android" build 8683349884183184033, revision 974d032a465edf08959681ed93a297ade2bd94c4 by Automatic Generated Files Sync · 4 hours ago
  3. 4d64536b Generated files from "codesearch-gen-chromium-ios" build 8683349884183183969, revision 974d032a465edf08959681ed93a297ade2bd94c4 by Automatic Generated Files Sync · 4 hours ago
  4. 3c8a73a Generated files from "codesearch-gen-chromium-chromiumos" build 8683349884183184017, revision 974d032a465edf08959681ed93a297ade2bd94c4 by Automatic Generated Files Sync · 4 hours ago
  5. 91bddcf1 Generated files from "codesearch-gen-chromium-fuchsia" build 8683349884183183985, revision 974d032a465edf08959681ed93a297ade2bd94c4 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.