Skip to content

GitHub sync for task boards

Sync GitHub issues and pull requests with task-board cards in both directions. Pull requests attach to the issue card they close, with check results and review decisions shown on the card. Board columns map to GitHub Projects v2 statuses. Write-back is optional; when disabled, the connector only reads.

Updated

Module · requires task boards

On the card

What GitHub puts on a board card

Launch board · In review

Release notes for 2.0

In review
#48 closes this issue
Checks passing Approved
Write changes back to GitHubOrganisation setting

  1. Status ↔ Projects v2

    Board columns map onto the project’s Status field.

  2. The pull request that closes it

    Attached to the issue’s card, not a card of its own.

  3. Checks and review

    Rollup and decision cached on the card.

  4. Write-back

    Off: the connector only reads. On: status and new issues go back.

How it works

Three layers, three permissions

How does the GitHub connection work?
Three layers, each behind a permission that already exists. An administrator makes one connection per organisation, with a GitHub App or a personal access token. Someone who may manage boards links a board to a repository, a Projects v2 project, or both. Each card then references the issue, pull request or project item it stands for.
What stops it writing to the repository by accident?
A per-organisation setting called “write changes back to GitHub”. With it off, a link stops writing and carries on reading, so tidying a board can never edit a repository. Every delivery is signature-verified, recorded before it is applied, and a replayed delivery is a no-op.
Connecting a GitHub repository to a board
Direction
GitHub to Enclessa always; back to GitHub is opt-in
What syncs
Issues, pull requests, Projects v2 status, checks, reviews
Card linking
A pull request attaches to the issue card it closes
Hosts
GitHub.com and GitHub Enterprise Server
Auth
A GitHub App or a personal access token, stored sealed
Requires
The task boards module

What it does not do

The edges, before you find them

  • Requires the task boards module: turning boards off turns GitHub off with it.
  • GitLab, Forgejo and Gitea have their own connector. There is no Bitbucket or Azure DevOps connector.
  • Enclessa does not host code, run pipelines or review diffs. The work stays in GitHub.
  • Write-back covers status and the issue a card was filed as. It is not a repository editor.
  • Managed rooms only. End-to-end encrypted rooms hold no server-side key, so nothing server-side can read or post in them.

FAQ

GitHub: questions

  • Yes. The GitHub module turns issues and pull requests into cards on an Enclessa task board and keeps them in step. A pull request that closes an issue attaches to that issue’s card, and the check rollup and review decision are shown on the card.

  • Only if the organisation switches write-back on. It is a per-organisation setting; with it off, the connector reads from GitHub and never writes to it, so moving a card cannot change a repository.

  • Yes. A connection stores the API host and the web host separately, because on GitHub Enterprise Server one cannot be derived from the other. Authentication is either a GitHub App or a personal access token.

Bring your team over this afternoon

Free for up to 10 people, with encrypted direct messages and video calls. No payment card, no time limit, no server to run.

For businesses and organisations only — not available to consumers.

Create your organisationCompare plans