Skip to main content

Indexing and Source Code

Providing source code now happens on the Indexing tab of the repository workspace (/repositories/:repositoryId/indexing). After the code is processed, the Insights and Source Code tabs unlock.

When to use​

  • Use Indexing after creating a repository, to connect or upload the code to analyze.
  • Use it again to reindex when the code has changed.
  • Use Source Code to browse the code that was indexed.
  • Use Insights to review the analysis produced from the indexed source.

Before you start​

  • Confirm the correct repository and the active organization.
  • For a ZIP upload, compress the source into a single .zip file and remove files that do not help the analysis.
  • For a Git connection, have the repository URL, the branch, and a read-only access token.

Choose a source​

The Indexing step offers two methods:

  • Connect a Git repository: import source from a hosted Git provider (Bitbucket Cloud) using a read-only token. You scan a branch and choose which paths to import. Credentials are used only for the import and are not stored. This is a one-time import — for automatic syncing on every push, use Git CI Integration instead.
  • Upload a ZIP file: add a source snapshot from your computer. The file must use the .zip extension and stay within the accepted size limit.

Step by step​

  1. Open the repository and go to Indexing.
  2. Choose Connect a Git repository or Upload a ZIP file.
  3. Provide the details for the chosen method and start the import.
  4. Wait for processing. Previous uploads and their processing state are listed on the same screen.
  5. When pre-analysis finishes, a banner reopens the confirmation dialog. Review files, lines, estimated tokens, and detected languages, then confirm to start indexing.

Insights​

The Insights tab summarizes what was found in the indexed source, across sections such as:

  • Overview: file and line statistics and the detected stack with a confidence score.
  • Languages: the language breakdown.
  • Cost estimates: estimated LLM cost, model context windows, and model recommendations when available.
  • Code composition: code, comments, and blank lines.

Insights replace the standalone pre-analysis review screen. For a full estimate of a documentation run, use Cost Explorer.

Source Code​

The Source Code tab lets you browse the indexed files. Source versions show their origin (a manual upload or a Git import) with clean file names.

Expected result​

The repository moves into processing, pre-analysis is confirmed through the indexer, and the Insights, Source Code, and Processes tabs become available.

See also​