Skip to content

docs(github): limited access still finds the baseline from commit history - #275

Open
jsfez wants to merge 1 commit into
mainfrom
docs/limited-access-baseline
Open

jsfez wants to merge 1 commit into
mainfrom
docs/limited-access-baseline

Conversation

@jsfez

@jsfez jsfez commented Nov 5, 2026

Copy link
Copy Markdown
Collaborator

The GitHub integration page said full access is "required for baseline selection based on commit history". That is not true anymore: without content access, the Argos SDK reads the commit history in the CI job, finds the merge base, and sends Argos the commit SHAs of the merge base and its ancestors (referenceCommit + /baseline lookups, parentCommits as a fallback). Argos picks the baseline among them.

Changes:

  • GitHub integration, Choose your access level: full access is still recommended (it doesn't depend on the CI checkout's history) and still required for Merge Queue; limited access now says the SDK finds the baseline from the CI checkout.
  • GitHub integration, new "How Argos finds the baseline without content access" under the limited access setup: what the SDK sends (commit SHAs, never file contents), the GitHub Actions pull_request test-merge case, what the checkout needs (origin remote, shallow clones fine), and the orphan + ARGOS_REFERENCE_COMMIT fallback.
  • Run Argos in CI and CLI reference: "connected to GitHub or GitLab, this happens server-side" becomes "connected to GitLab, or to GitHub with full access".

Left as is: "Merge Queue is not supported" with limited access, not re-checked here.

Merges cleanly with #273, which touches the same three pages in other sections.

🤖 Generated with Claude Code

…tory

The access level section said full access was required for baseline
selection based on commit history. Without content access, the SDK reads
the history in the CI job instead: it finds the merge base, sends the
commit SHAs of the merge base and its ancestors, and Argos picks the
baseline among them. Say so, explain what the CI checkout needs, and stop
saying in the CI and CLI pages that any GitHub project resolves it
server-side.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jsfez
jsfez requested a review from gregberge November 5, 2026 15:57

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants