Pins that close themselves
Connect GitHub, write "Fixes ACME-42" in a PR, and the pin resolves when it merges. Nobody has to go back and tidy up.
The last step of fixing a pin is the one everyone forgets: going back and marking it done. Agents are pretty good about it, but people merge PRs at odd hours, from their phone, long after the session that wrote them has gone.
So now GitHub does it.
How it works
A workspace owner connects GitHub from the Workspace page. After that, Laterbase reads each pull request's title, description and branch, and each pushed commit's message, for pin keys from that workspace.
- "Fixes ACME-42" (or "closes" or "resolves") links the PR to the pin as its fix. A list works too: "Fixes ACME-1, ACME-2 and ACME-3".
- Any other mention of a pin key links it as related, so it shows up in the pin's history.
- When the PR merges, the pin resolves. It even resolves over someone's claim, since the work's done either way.
GitHub shows up in each pin's history as its own user, along with who merged, so you can always see why a pin changed.
Works with your agent, not instead of it
Agents already link their PR to the pin as soon as it's open, and resolve the pin once it merges. Whichever gets there second is a quiet no-op, so there's no double-counting and nothing to clean up.
To connect it, see GitHub in the docs.