# GitHub

Add release decisions and findings to pull requests, and see who used Copilot on the days behind each release. Open the **GitHub** card on the Integrations page; each part has its own status and setup.

## GitHub App

The Bumpkit GitHub App adds a release gate check you can require in branch protection, handles merge queues and re-runs, and annotates findings on the exact lines.

Every pull request check runs once per event, even when GitHub delivers the event twice. A newer push replaces a check that hasn't started yet, and a late event for an older commit never replaces the check of the latest one. If Bumpkit hits an error, it retries the check automatically. If it still can't finish, **Bumpkit release gate** fails with "Bumpkit couldn't finish this check"; push a commit or re-run the check to try again. The Checks page, `bumpkit checks queue` and the `checks_queue` MCP tool show which checks are queued, running, retrying or failed.

```bash
bumpkit repo add acme/shop
bumpkit repo list
```

The `repo_add` and `repo_list` MCP tools do the same. See [repository setup](/docs/quickstart-engineering) and [Release Gate](/docs/release-gate#the-github-app).

## GitHub Actions

Run the release gate as a job in your own workflow. See [Run it in GitHub Actions](/docs/release-gate#run-it-in-github-actions).

## GitHub Enterprise Server

> **Beta, early access.** Flags: `github_enterprise_server` and `release_gate`.

Run the release gate on pull requests on your own server. Connect a repository with an access token, add one webhook, and Bumpkit reads the policy from the default branch on your server, counts reviews on the latest commit, and reports a **Bumpkit release gate** commit status and one comment.

1. On your server, create a personal access token with the `repo` scope, from a user who can write to the repository. Add `read:org` if your rules name teams.
2. Connect the repository. Use the **GitHub Enterprise Server** section on the GitHub card on the Integrations page, or the CLI:

   ```bash
   bumpkit gate connections add --provider ghes --host https://github.acme.example --path acme/api
   ```

3. In the repository's **Settings → Hooks → Add webhook**, paste the webhook URL into **Payload URL**, set **Content type** to `application/json`, and paste the secret into **Secret**. Choose **Pull requests**, **Pull request reviews**, **Check runs** and **Statuses**. Bumpkit shows the secret only once.
4. Open a pull request. The status and the comment appear within a minute. To block merges, require **Bumpkit release gate** in the branch protection rule under **Settings → Branches**.

The `gate_connections_add` and `gate_connections_list` MCP tools do the same. Owners and admins connect. Your server must be reachable from the public internet. See [Release Gate](/docs/release-gate#github-enterprise-server).

## GitHub Copilot usage

See who used Copilot on which day, with no developer setup. Connect a fine-grained token with the Organization Copilot metrics read permission, or a classic token with `read:org`, from an org owner. Copilot usage metrics must be on for the organization.

```bash
bumpkit agents vendors connect copilot --key-file - --org acme
```

The `agent_vendors_connect` MCP tool does the same. Owners and admins connect. See [AI vendor usage](/docs/vendor-usage).