Link GitHub to your cards
The GitHub connector links pull requests and commits to the cards they mention, moves statuses along with the code, and imports a repository's issues into a list — with no duplicates on the second run.
The GitHub connector lives in Settings → Marketplace, on the Developer shelf. Like Slack and Google Drive, it is a separate service that only uses the public Spunto CMS API.
The result: a PR named spr-12-login moves SPR-12 to "In review" and leaves its
link there; merging it completes the card; the repository's issues live in a
list.
Install
- Install from the listing, then give your consent for the space. The
connector asks for the member role and three scopes:
items:read,items:write,schema:read. It writes to your cards, but creates no property, status or view — and hooks no webhook into the space. - Install on GitHub: GitHub asks you to pick the account or organization, and the repositories the connector may read. If the app is already installed on your organization, Link an existing installation is enough.
- Follow a repository, then set what it does.
Only a space admin can install a connector.
What links a PR to a card
A card key (SPR-12), case-insensitive:
| Where | Effect |
|---|---|
| PR title, branch name | links and applies statuses |
description, after fixes, closes or resolves | links and applies statuses |
| description, anywhere else | links only |
| commit message | links only |
#42 targets the card of issue 42, when the repository's issues are imported.
Beyond ten mentioned cards, the rest are ignored.
A repository's settings
Write the link into — a URL property of the space (create one, "Pull request", if you have none). An empty field gets the first link; a new PR replaces the previous link; a commit never replaces a PR.
PR opened → / PR merged → — the statuses to apply. "PR opened" also counts a reopened PR or one marked ready for review. An opened PR never moves a card that is already done back; pushing to the branch doesn't reset the status. The card's history shows these changes, signed by the app.
Issues — the list to put them in, and the statuses for an open or closed issue. Sync issues imports the whole repository; afterwards, every issue created, edited, closed or reopened follows on its own. Replaying the sync only rewrites what changed on GitHub. Imports don't show up in the activity feed filtered to activity.
What GitHub owns on an issue card: the title, the description (if the issue has one), the status when the issue's state changes, and the link at creation. Properties you add to the card stay yours.
Without a configured GitHub app
If the instance has no GitHub app, the screen offers to connect a repository
by hand: it gives a URL and a secret to paste on GitHub (Settings →
Webhooks, application/json, events Pull requests, Pushes and Issues).
Everything works except the full issue sync: issues arrive as they change.
What it doesn't do
- It writes nothing on GitHub: no comment, no commit status.
- A deleted issue doesn't delete its card.
- A card carries one link in the chosen property, not the list of all its PRs.
- Uninstalling happens in the space settings; cards and imported issues stay.