Clone this repo:

Branches

  1. a60ddd7 Generated files from "codesearch-gen-chromium-win" build 8689442530973106737, revision a61ec31b6854a2bfd607ac653eb6043ff2fcd88b by Automatic Generated Files Sync · 2 hours ago main
  2. 5dfed8742 Generated files from "codesearch-gen-chromium-mac" build 8689442531369871265, revision a61ec31b6854a2bfd607ac653eb6043ff2fcd88b by Automatic Generated Files Sync · 2 hours ago
  3. bca25128 Generated files from "codesearch-gen-chromium-android" build 8689442531406987505, revision a61ec31b6854a2bfd607ac653eb6043ff2fcd88b by Automatic Generated Files Sync · 2 hours ago
  4. b66d50d Generated files from "codesearch-gen-chromium-chromiumos" build 8689442531296087969, revision a61ec31b6854a2bfd607ac653eb6043ff2fcd88b by Automatic Generated Files Sync · 2 hours ago
  5. 22f2d05 Generated files from "codesearch-gen-chromium-linux" build 8689442532365005937, revision a61ec31b6854a2bfd607ac653eb6043ff2fcd88b by Automatic Generated Files Sync · 2 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.