Merge the branch. The issue closes itself.
Name a branch after an issue, or press ⌘⇧. to copy the name Keel suggests. From then on, Burrow tells Keel what happened: opened, reviewed, merged, reverted.
Offline queue for comments on mobile
HAL-219 · Backlog
- Lea pushes a branchlea/hal-219-offline-queueBurrow
- HAL-219 moves to In progress and links the branchKeel
- Pull request #482 opened, Jonas asked to reviewPR #482 · 6 filesBurrow
- HAL-219 moves to In review; Jonas sees it in his inboxKeel
- #482 merged into mainmain · 3f9c21aBurrow
- HAL-219 moves to Done and counts toward Cycle 24Keel
Burrow, wired into the work.
- ⌘⇧.
Branch names you never type
Copy the branch name from any issue. It carries the key, your handle and a short slug.
Status follows the code
Draft PR, ready for review, merged, reverted. Each one maps to a status you choose per team.
Many PRs, one issue
An issue closes when its last linked pull request merges, not its first.
Reverts reopen
Revert the merge and the issue goes back to In progress with a comment saying why.
Commit magic words
“Fixes HAL-214” in a commit message links and closes, the way you already write it.
Three steps, about 2 min.
- 01Install the Keel app on your Burrow organization
- 02Pick the repositories Keel may read
- 03Choose which status each PR event maps to
What it can see, in writing.
- reads
- branch names, PR titles, review state, merge events
- writes
- one comment per PR with the issue link (optional)
- never
- source code, diffs or secrets
- webhooks
- signed, retried for 24 h with backoff
About Burrow.
Often connected together
Connect Burrow in 2 min.
Available on every plan, Free included. Start a workspace, then add it from Settings → Integrations.