Clone this repo:

Branches

  1. b62a97ea Generated files from "codesearch-gen-chromium-mac" build 8687494696436709697, revision d440c7a5d5c57f12f20de23c8ea8bf998f147bf4 by Automatic Generated Files Sync · 3 hours ago main
  2. c975c90 Generated files from "codesearch-gen-chromium-win" build 8687494696759173569, revision d440c7a5d5c57f12f20de23c8ea8bf998f147bf4 by Automatic Generated Files Sync · 3 hours ago
  3. 79dced2 Generated files from "codesearch-gen-chromium-android" build 8687494697434651521, revision d440c7a5d5c57f12f20de23c8ea8bf998f147bf4 by Automatic Generated Files Sync · 3 hours ago
  4. 75c7c35 Generated files from "codesearch-gen-chromium-fuchsia" build 8687494696820149377, revision d440c7a5d5c57f12f20de23c8ea8bf998f147bf4 by Automatic Generated Files Sync · 4 hours ago
  5. 3cd36e6 Generated files from "codesearch-gen-chromium-chromiumos" build 8687494696885279857, revision d440c7a5d5c57f12f20de23c8ea8bf998f147bf4 by Automatic Generated Files Sync · 4 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.