Clone this repo:

Branches

  1. bf0fe8a4 Generated files from "codesearch-gen-chromium-android" build 8714337815183700641, revision f3aa4bf097d4789baea692dec7a73cba97281ab8 by Automatic Generated Files Sync · 2 hours ago main
  2. 734c139 Generated files from "codesearch-gen-chromium-win" build 8714337813970606945, revision f3aa4bf097d4789baea692dec7a73cba97281ab8 by Automatic Generated Files Sync · 2 hours ago
  3. 1eec40b7 Generated files from "codesearch-gen-chromium-linux" build 8714337814125559393, revision f3aa4bf097d4789baea692dec7a73cba97281ab8 by Automatic Generated Files Sync · 3 hours ago
  4. 5460773 Generated files from "codesearch-gen-chromium-mac" build 8714337815308169153, revision f3aa4bf097d4789baea692dec7a73cba97281ab8 by Automatic Generated Files Sync · 3 hours ago
  5. 9607aac Generated files from "codesearch-gen-chromium-fuchsia" build 8714337815098169841, revision f3aa4bf097d4789baea692dec7a73cba97281ab8 by Automatic Generated Files Sync · 3 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.