Use
Integrations
GitHub is live. Jira, Linear, Slack and Microsoft Teams are ready for you to connect. GitLab, Bitbucket and Azure DevOps adapters are built; reviews on them switch on in a coming release.
In testingIntent check is built and being verified end to end. This page describes how it works once it is switched on for your workspace.
Connections are managed on the Integrations page of the app by owners and admins. Credentials are encrypted at rest, every connection has a Test connection button, and you can disconnect at any time.
Status at a glance
| Integration | What it does | Status |
|---|---|---|
| GitHub | Reviews, commands, check runs, intent from linked issues | Live |
| GitLab | Merge request reviews | Coming |
| Bitbucket | Pull request reviews | Coming |
| Azure DevOps | Pull request reviews | Coming |
| Jira | Acceptance criteria for the intent check | Ready, connect your account |
| Linear | Acceptance criteria for the intent check | Ready, connect your account |
| Slack | Merge-readiness digests | Ready, connect your account |
| Microsoft Teams | Merge-readiness digests | Ready, connect your account |
Ready, connect your account means the integration is built and tested against recorded examples, and goes live for your workspace when you connect it with your own credentials.
GitHub
The GitHub App is how Forseti reviews today: inline comments with suggestions, the sticky summary, one check run per commit, @forseti commands, and linked GitHub issues for the intent check. Setup and permissions are in Install the GitHub App.
GitLab, Bitbucket and Azure DevOps
Each adapter does the same job as the GitHub App, in the host's own terms. The adapters are built and tested against recorded traffic; reviews on these hosts switch on in a coming release, so the Integrations page does not accept them yet.
| Host | You provide | Webhook check | Comments and status |
|---|---|---|---|
| GitLab | An access token, and your instance URL if self-managed | Secret token header (X-Gitlab-Token) | Merge request discussions on the changed lines; commit status |
| Bitbucket | Workspace, username and an app password | HMAC signature | Inline pull request comments; build status |
| Azure DevOps | Organisation URL and a personal access token | Basic auth or a shared secret header | Pull request threads; pull request status |
Each connection receives the host's merge request or pull request events through its own webhook, verified as above. Once live for your workspace, reviews follow the same depth, policies and caps as on GitHub.
Jira and Linear
The intent check asks whether a pull request does what its work item asked. Forseti finds the work item from GitHub closing references, issue links in the description, the branch name (for example feat/123-…), and, once Jira or Linear is connected, keys such as ABC-123. It extracts the acceptance criteria and rates each one met, unmet or unclear, with file and line evidence. It never blocks a merge by default.
| Tracker | You provide |
|---|---|
| Jira | Site URL, account email, API token and the project keys to look up |
| Linear | API key and team key |
Slack and Microsoft Teams
Paste an incoming webhook URL and Forseti posts a merge-readiness digest, daily or weekly at the hour you choose (UTC): open PRs with conflicts, failing or pending checks, missing or stale approvals, review lag, and Forseti's own verdict. Send test posts a sample straight away.