How the required read-only GitHub connection improves recommendation quality without broad repo mirroring or write access.

Each ShipFoundry project requires one selected GitHub repository. ShipFoundry uses that read-only connection to decide whether an external update appears to touch the product. Relevant proof is still evidence-dependent and may be unavailable for a specific match.

When To Use This

Use GitHub when code-level relevance matters. It is useful for framework changes, package changes, SDK upgrades, config shifts, auth or billing integration changes, and other updates that should be checked against a real repo.

The connected repository is required to finish project setup. A match can still produce a research, workflow, or strategy brief when a bounded check does not find applicable implementation proof.

How It Works

ShipFoundry uses selected repositories first. Repo evidence should be focused and tied to an update, project, and commit context.

The goal is not to mirror the whole repo. The goal is to collect enough evidence to support or weaken a specific recommendation.

Step-By-Step

Connect GitHub from the project or integrations settings flow.
Select the repositories ShipFoundry may inspect.
Let ShipFoundry collect lightweight repo context and focused evidence.
Open a relevant update.
Compare source evidence with repo evidence.
Use the trust state to decide whether to investigate, hand off, defer, or ignore.

What ShipFoundry Does

Treats one selected GitHub repository as required project context.
Uses read-only access for selected repositories.
Looks for focused evidence related to specific updates.
Shows evidence separately from source summaries.
Uses repo evidence to strengthen or weaken handoff readiness.

What ShipFoundry Does Not Do

It does not commit code.
It does not open PRs.
It does not edit workflows.
It does not request broad write access for this evidence path.
It does not claim to scan secrets unless a later product decision implements and documents that capability.
It does not mirror every file in a repo by default.

Trust Language

Boundary	Product Meaning
Required Connection	One selected read-only repository is required to finish project setup.
Evidence-Dependent Proof	A specific match may have no applicable repository proof.
Read-Only	Repo evidence should inform recommendations, not mutate code.
Selected Repositories	Users choose which repos are in scope.
Evidence, Not Authority	Local review, tests, and code review still decide what ships.

Troubleshooting

If GitHub is connected but no evidence appears, the update may not be code-relevant, the repo may not be selected, or the focused check may not have found proof.

If evidence looks stale, refresh project context and confirm the repository connection still points at the expected repo.

If evidence seems wrong, record the outcome and narrow the product context or ignored sources.

Trust states: Trust And Readiness
Brief format: Investigation Briefs
Agent workflow: Agent Workflows
Example artifact: Sample Engineering Spike
First setup path: Quickstart
Product CTA: Start 7-Day Trial

Was This Page Useful?

Send a short note if this page is unclear, overclaims a capability, or is missing the proof you expected.

Send Docs Feedback

GitHub Repo Evidence