Git providers

Connect your GitHub or Bitbucket account and Every links development work to tasks automatically: name a branch after a task reference and the branch, its commits, and its pull requests show up on the task.

Connecting

An admin connects the integration under Administration → Integrations: choose Connect GitHub or Connect Bitbucket and approve the OAuth request. Then, in the integration's Manage panel, pick which organisations (or Bitbucket workspaces) to Monitor.

Monitoring is org-level and hands-off: Every registers a webhook, discovers all the repositories, and picks up new repositories automatically as they're created. No per-repo setup.

Linking work to tasks

The link is the task reference. Every scans incoming activity for references like GO-6 in:

• Branch names: go-6-fix-checkout
• Commit messages: Fix rounding in totals (GO-6)
• Pull request titles and source branches

Matching is case-insensitive, one branch or PR can reference several tasks, and references keep working even if a task's prefix has changed since (old references are remembered).

So the developer workflow is just: grab the task reference, put it in your branch name, and work normally. No plugin, no manual linking.

What you see on the task

Linked git activity appears on the task: branches, commits, and pull requests with live status (open, draft, merged, or closed, colour-coded), each linking back to GitHub or Bitbucket. Task cards on the board carry small indicators too, so "is there a PR for this yet?" is answerable without opening anything.

This closes the loop for non-developers: an account manager can see that GO-6 has a merged PR without leaving Every or learning GitHub.

Disconnecting

From the same Integrations page: stop monitoring individual organisations, or Disconnect the provider entirely, which revokes Every's access. History already linked to tasks stays put.