> ## Documentation Index
> Fetch the complete documentation index at: https://docs.incident.io/llms.txt
> Use this file to discover all available pages before exploring further.

# GitHub

> Link pull requests to incidents and keep follow-ups moving, without leaving GitHub.

Are you using GitHub for version control, or to track your team's tasks?

You should consider installing our integration

***

## What our GitHub integration can do

Our integration lets you:

### 1. Export your incident to-dos to GitHub

You can export your follow-ups to GitHub. We'll sync the status of your tasks, so you can work in GitHub without worrying about updating statuses manually in incident.io!

On an incident's **Post-incident** tab, open a follow-up's menu and choose **Create or link a GitHub issue**:

<img src="https://mintcdn.com/incidentio-18bb4170/XsSsM18yW6o4p-bZ/images/help-centre/github/screenshot-1.png?fit=max&auto=format&n=XsSsM18yW6o4p-bZ&q=85&s=43b95841f367d3585785f3d7028f1124" alt="A follow-up menu on the Post-incident tab, open on Create or link a GitHub issue" width="1496" height="792" data-path="images/help-centre/github/screenshot-1.png" />

You can also create export templates and [automatically export follow-ups](/integrations/auto-export-follow-ups). In your templates, you can use expressions to set GitHub labels dynamically, for example tagging follow-ups by team or priority.

Changes in GitHub update the linked follow-up: the issue title, its body as the description, its labels, and its assignee as the follow-up owner. Closing the issue completes the follow-up, and records when it was closed.

#### 2. Attach GitHub pull requests to incidents

When you drop a link to a GitHub PR in your incident channel, we'll ask if you want to add it as an [attachment](/incidents/attachments). Once it's attached, we'll notify the channel about changes to that PR, for example if it gets merged.

<img src="https://mintcdn.com/incidentio-18bb4170/T7N4DImO02Rr9Lqz/images/help-centre/github/screenshot-2.png?fit=max&auto=format&n=T7N4DImO02Rr9Lqz&q=85&s=ab8ffcaab14f0e2610190e96fa27897f" alt="An image showing incident.io notifying the incident channel when a PR is merged." width="600" height="169" data-path="images/help-centre/github/screenshot-2.png" />

#### 3. Track each incident as a GitHub issue

Set up [incident tickets](/integrations/incident-tickets) to create a GitHub issue for each incident and keep it up to date. Add the **State** field to your template to open and close the issue from the incident.

***

## Setting Up

Adding GitHub to incident.io is simple.

1. **Go to Settings** → [Integrations](https://app.incident.io/~/settings/integrations)

Hit `Connect` next to GitHub.

<img src="https://mintcdn.com/incidentio-18bb4170/T7N4DImO02Rr9Lqz/images/help-centre/github/screenshot-3.png?fit=max&auto=format&n=T7N4DImO02Rr9Lqz&q=85&s=09c9a0a4ce79899f69fdd8f18830fc2e" alt="The Integrations settings list with Connect highlighted on the GitHub row" width="2824" height="2296" data-path="images/help-centre/github/screenshot-3.png" />

2. **Install incident.io**

*Your GitHub account* **must be an Organization** *(not a personal account). Enterprise customers can connect multiple organizations. [Get in touch](mailto:support@incident.io) to set this up.*

<img src="https://mintcdn.com/incidentio-18bb4170/T7N4DImO02Rr9Lqz/images/help-centre/github/screenshot-4.png?fit=max&auto=format&n=T7N4DImO02Rr9Lqz&q=85&s=2721d1fc35f68cafa9ab380af80b55d5" alt="GitHub's Install incident-io page, asking which account or organization to install into" width="1224" height="1418" data-path="images/help-centre/github/screenshot-4.png" />

That's it!

<Info>
  **GitHub Enterprise Server** and **multiple GitHub organization** support are available for enterprise customers. [Get in touch](mailto:support@incident.io) to get set up.
</Info>

If you run into any issues, [get in touch](http://incident.io/community)
