Clone this repo:

Branches

  1. 694606f Generated files from "codesearch-gen-chromium-cronet" build 8690031404027112737, revision 98a0a85591d6c028de44754a6bb8d0b4941c5b11 by Automatic Generated Files Sync · 11 minutes ago main
  2. 2113673a Generated files from "codesearch-gen-chromium-mac" build 8690054067779339777, revision ff15eaa2a6d643f6ba63fc946220d5fc6da82044 by Automatic Generated Files Sync · 40 minutes ago
  3. c48e7bf Generated files from "codesearch-gen-chromium-chromiumos" build 8690054067216866081, revision ff15eaa2a6d643f6ba63fc946220d5fc6da82044 by Automatic Generated Files Sync · 4 hours ago
  4. 93689ad Generated files from "codesearch-gen-chromium-win" build 8690054067971527457, revision ff15eaa2a6d643f6ba63fc946220d5fc6da82044 by Automatic Generated Files Sync · 4 hours ago
  5. 3a9078b Generated files from "codesearch-gen-chromium-android" build 8690054067859887569, revision ff15eaa2a6d643f6ba63fc946220d5fc6da82044 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.