GitHub integration
Branches, pull requests, commits, CI runs and releases linked to the work they belong to, kept current automatically.
How work links itself
Every work item has a code, such as PBI-364. Written in a branch name, a pull request, a commit message or release notes, it links that GitHub activity to the item automatically; the project's key and the number, such as PAGOS-364, works too.
- Pull requests show their live state, whether they are drafts and their review outcome.
- A branch can be created on GitHub from the item itself, already named after it.
- A pasted URL of a linked repository is stored as that GitHub object, never as a duplicate.
Connecting
- Connect through the general GitHub service, with nothing to register.
- Or use your organization's own OAuth App, including GitHub Enterprise Server.
CI/CD and releases
- GitHub Actions runs and commit statuses from any other CI show on the items they ran for.
- Published releases mark the items their notes mention as shipped.
- A report tab summarizes pipeline success, duration, releases and open pull requests.
- A Deployment with a linked pull request meets the Pull Request requirement to leave Development.
Always current
- Each item shows its development progress, from branch to release.
- Webhooks report changes as they happen; open links are also re-checked every 30 minutes.
- Each workspace's administrator sees its connection health, API quota, activity, errors and every linked repository.
Security
- The access token is stored encrypted and never shown or logged.
- Webhook deliveries are verified by signature, size-limited and reduced to the fields used.
- The webhook secret can be rotated without interrupting deliveries.
- Each project reaches only its own repositories, and each user only the items they can see.