Skip to content
Keel
Integrations Code

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

  1. Lea pushes a branchlea/hal-219-offline-queueBurrow
  2. HAL-219 moves to In progress and links the branchKeel
  3. Pull request #482 opened, Jonas asked to reviewPR #482 · 6 filesBurrow
  4. HAL-219 moves to In review; Jonas sees it in his inboxKeel
  5. #482 merged into mainmain · 3f9c21aBurrow
  6. HAL-219 moves to Done and counts toward Cycle 24Keel
What it does

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.

Set it up

Three steps, about 2 min.

  1. 01Install the Keel app on your Burrow organization
  2. 02Pick the repositories Keel may read
  3. 03Choose which status each PR event maps to
Permissions

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
Questions

About Burrow.

Connect Burrow in 2 min.

Available on every plan, Free included. Start a workspace, then add it from Settings → Integrations.