Boomship/Integrations / GitHub
GitHub, exactly.
A connected repository is what Build Missions read, change and prove.
What Boomship does with GitHub
GitHub
CodeA connected repository is what Build Missions read, change and prove.
- Reads
- Indexes a repository into the project’s Brain: its code, its symbols and what imports what.
- Writes
- Commits a Mission’s change to a boomship/ branch. Never to your main branch.
- Verifies
- Fetches a pull request, tests it in a sandbox and reviews it before you merge.
- Cannot
- Push to your main branch or merge. On a host with no shell it edits through the git-data API and runs nothing, so tests stay “not run” there.
- Permission
- A GitHub token you store. Encrypted; only its last four characters are ever shown again.
Act 01Where it shows up
Missions that use GitHub.
Each template below names this service as a tool, says whether it is required, and why. Start one as it is, or change the sentence.
- Build this issue
Build Linear issue NS-412 and open a pull request.
required · the repository Boomship reads, changes and proves - Verify this release
Verify pull request northstar/web#128 before I merge it.
required · a stored token reads the pull request; the sandbox never sees it - Audit onboarding
Walk through onboarding on northstar.example, find what breaks, and fix it.
required · the repository the fix lands in - Investigate a metric
Activation drops 38% between account creation and the first catalogue. Find out why.
optional · the code behind the funnel, when the metric is in your product