Skip to main content

​
Repository sync & refresh

Repository-backed Knowledge is only useful when Starfire knows which source revision it analyzed.

​
Connect a repository

When repository integration is available:
  1. Connect the supported repository provider through the integration layer.
  2. Select the intended repository.
  3. Choose the branch or revision context supported by the current build.
  4. Associate it with the correct Project or organization.
  5. Wait for repository indexing or metadata preparation to complete.

​
Source revision matters

A repository can change after Starfire indexed it. Build plans and code answers should be interpreted against the revision that was actually analyzed. If a major merge or refactor happened, refresh repository context before asking Starfire to make another cross-file change.

​
Branch awareness

Different branches can contain different APIs, dependencies, or architecture. Do not assume knowledge prepared from main accurately represents an active release branch or feature branch.

​
Refresh strategy

Refresh when:
  • dependencies changed
  • directories moved
  • a major feature landed
  • build configuration changed
  • the branch changed
  • repository access was reconnected
  • Starfire repeatedly references files that no longer exist

​
Credentials

Repository credentials belong in the integration layer. Never place personal access tokens, deploy keys, or OAuth tokens in project instructions or chat prompts.

​
FORGE handoff

A repository-backed FORGE job should record enough source context to identify what it inspected before changing files. If the source revision changes while a build is running, avoid assuming the final artifact automatically includes those newer changes.
Repository synchronization behavior depends on the connected provider and current Alpha implementation. The source revision shown by Starfire is the stronger reference than a generic “latest” assumption.