Clone this repo:

Branches

  1. 8fdaa3f Generated files from "codesearch-gen-chromium-win" build 8690144612034189217, revision 17bcef300e8198f2a426a8a2f561b833a1ae2da4 by Automatic Generated Files Sync · 4 minutes ago main
  2. 6533f8e Generated files from "codesearch-gen-chromium-mac" build 8690144611371252241, revision 17bcef300e8198f2a426a8a2f561b833a1ae2da4 by Automatic Generated Files Sync · 9 minutes ago
  3. 316b171 Generated files from "codesearch-gen-chromium-linux" build 8690144611308230913, revision 17bcef300e8198f2a426a8a2f561b833a1ae2da4 by Automatic Generated Files Sync · 33 minutes ago
  4. 4aed1f56 Generated files from "codesearch-gen-chromium-ios" build 8690144611659465889, revision 17bcef300e8198f2a426a8a2f561b833a1ae2da4 by Automatic Generated Files Sync · 84 minutes ago
  5. f2073f6 Generated files from "codesearch-gen-chromium-webview" build 8690144612032061777, revision 17bcef300e8198f2a426a8a2f561b833a1ae2da4 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.