GitHub

Let your pull requests move your tickets for you.

Nobody enjoys dragging a card across the board after they have already merged the code. Connect GitHub once and Cohively watches your pull requests instead: mention a ticket in the branch name, the title or the description, and the ticket follows the work from in-progress to review to done on its own.

Get started Explore all features

What it looks like

Any of these three links a pull request to ticket COH-9. The board reference is the one shown on the ticket itself.

branch   feature/coh-9-add-the-widget
title    COH-9 Add the widget
body     Closes COH-9

How to connect

A few minutes, once. Then it looks after itself.

Install the app

Open Administration → Integrations in your workspace and choose Connect GitHub. You pick on GitHub which repositories Cohively may see — all of them, or only the ones that matter.

Point repositories at projects

Each repository is assigned to one project from that project's own settings, so a ticket reference always resolves to the right board.

Name a ticket in your pull request

Put the reference in the branch name, the title, or after a closing keyword in the description. Cohively links the pull request and moves the ticket as it progresses.

Why teams turn it on

Get started

The board stops going stale

A ticket moves when the code moves, not when somebody remembers to update it. Drafts land in progress, open pull requests in review, merges in done.
It respects your judgement

Move a ticket yourself and it stays where you put it. Only a merge or a close overrides you, because those are facts about the code rather than guesses about intent.
Read-only on your code

Cohively asks for read access to pull requests and metadata, and nothing else. It never pushes, comments, or writes anything back to GitHub.
You can see who did what

Every automatic move is written to the board activity log, attributed to the integration rather than to whoever happened to be signed in.

The details

Permissions requested: Pull requests: read. Metadata: read. Nothing that can change your repositories.
Who can connect it: A workspace administrator with permission to manage settings. One GitHub account or organisation connects to one workspace.
What you can configure: Which board column a draft, an open, a merged and a closed pull request each lead to — or leave any of them alone. Reference detection and automatic moves can both be switched off.
Continuous integration: A pull request on a ticket shows whether its checks passed, failed or are still running.
Disconnecting: Disconnect from the same settings page and Cohively uninstalls itself from GitHub. Uninstalling on GitHub instead only pauses syncing — your links are kept until you disconnect on purpose.