Build this issue.
An issue in, a verified change on a boomship/ branch out. The merge stays yours.
What you give it.
A sentence, and what the Brain already holds. Boomship asks for a repository or a file only when the Mission needs one.
Build Linear issue NS-412 and open a pull request.
Northstar Supply, a fictional company · Illustration
What it does with it.
Each step names what it makes. Every step that ran is on the receipt; one that could not run is written as not run.
- 01Read the issue and the code it namesa context plan, every item with a reason
- 02Plan the changefiles, symbols, importers
- 03Build ita boomship/ns-412 branch
- 04Verify itfresh tests, typecheck, an independent review
- 05Open the pull requesta Work Receipt on the PR
What comes back.
Your first order in nine minutes.
Northstar v4 sets up your catalogue from last month’s invoices.
Start with an invoice- A pull request from a boomship/ branch, never your main branch
- A Work Receipt: tests, typecheck, review, secrets, every check named
- What could not run, written as not run
What it needs connected.
Each one says how it connects and what Boomship may do with it. A connection on its own puts nothing into a Mission; only what you add to a project’s Files does.
Where you come in.
A steer is received at the next turn. A failed check holds a chain. The merge is a button Boomship does not press.
- Steerwhile it works
Send a line; it is received at the next turn and the route changes.
- Reviewwhen the receipt arrives
Read the verdict and the findings before you look at the diff.
- Mergeat the end
Boomship opens the pull request. Merging is yours.