GitHub repository connection
Connect a repository so ShipFoundry can check recommendations against your code.
Each project needs one connected GitHub repository. ShipFoundry reads it to check whether a software update affects your implementation and to give your agent specific files to inspect.
Connect a repository
- Open the project's setup page and connect GitHub.
- In GitHub, approve access to the repositories you want ShipFoundry to read.
- Back in ShipFoundry, select the repository for this project.
- Check setup status before starting the first review.
An agent can list and select repositories after you approve GitHub access. See agent setup for the MCP, API and CLI steps. GitHub consent stays in the browser.
What the connection provides
Recommendations can include file references and evidence tied to the repository and commit that were checked. Read these alongside the original release note or source document.
A connection alone does not establish that an update applies. A check may find direct evidence, a possible connection, or no supporting code. The readiness state records that distinction. Updates about operations or product decisions may still matter without a code change.
When your agent takes the work, have it check the current checkout. Files may have changed since ShipFoundry reviewed them. The brief and task packet give it the findings, remaining questions and checks to run.
Initial findings and deeper checks
ShipFoundry searches the repository index before producing a recommendation. On the recommendation page, Initial Repository Check Complete shows the retained file references, evidence grade and checked revision. Contextual findings can explain why an update matched without proving that it is worth adopting.
A deeper repository check is separate. When no deeper check was automatically scheduled, an open recommendation with a connected repository offers Run Repository Check. This uses the account's repository-check allowance. Queued or running work continues without a second launch. Closed recommendations preserve their findings without asking you to start new work.
You can also use Copy Investigation Plan with your connected coding agent. It inspects the local checkout and records the findings in ShipFoundry for you to review.
Access
This connection is read-only. ShipFoundry does not use it to edit files, create commits, open pull requests or change workflows. Repository checks collect evidence for recommendations; they do not provide a secret-scanning service or mirror every file by default.
Your coding agent's permission to change code is separate from ShipFoundry's GitHub access.
If evidence is missing or stale
- Confirm that the project has the intended repository selected and GitHub access is still valid.
- Check the referenced commit and files. Refresh project context when the implementation has changed.
- Read the missing-evidence notes. A completed search may find no applicable code; repeating it is not necessarily useful.
- If your agent finds that a recommendation is wrong, record its finding as an outcome with the inspected paths.
Continue with reviewing updates with an agent or setting up a project.