- Send notification-free events from GitHub or GitHub Enterprise to PagerDuty services regarding important changes, such as new pull requests and commits, to provide context for PagerDuty users.
- Users may review change events within a PagerDuty service’s Recent Activity timeline during incident triage or hypercare. They can also see recent changes on the service’s incidents, and navigate across all changes in a comprehensive list of Recent Changes across all services.
In PagerDuty: This integration requires a Manager base role or higher to configure.
In GitHub: This integration requires an Admin role to configure.
- When a GitHub pull request is closed and the branch is merged, a webhook will be sent to the endpoint of the integrated PagerDuty service.
- These events will be viewable as change events in the service’s Recent Activity timeline on incidents associated with that service, and in a global list of all change events.
- In the PagerDuty web application, navigate to Services Service Directory and click the name of your preferred service.
- Select the Integrations tab and click Add an integration.
- Search and select GitHub, then click Add.
- On the next screen, find GitHub in the list of integrations and click to reveal the integration details.
- In the section Integration URL, click to copy the integration URL to your clipboard. It will be in the following format:
- Keep the URL in a safe place, since you will use it in the next section.
By default, the integration tracks the
masterbranch. To edit this behavior, please refer to the section Branch Tracking
- Navigate to the GitHub repository where you would like to track changes, select the Settings tab, and then select Webhooks.
- Click Add webhook on the right.
- Paste the Integration URL that you generated in PagerDuty (above) into the Payload URL field, and in the Content type dropdown select
- Under Which events would you like to trigger this webhook? select Let me select individual events. Check the box next to Pull requests and uncheck the box next to Pushes.
- Ensure that the Active checkbox is selected, enter any other preferred settings, and click Add webhook.
This integration also supports push events, but they will show less information in PagerDuty. The pull request event is recommended if you use GitHub's pull request functionality. Since selecting both pull request and push events may result in two change events for a single action, we recommend selecting just one or the other.
To test the integration, merge a pull request to the branch that you are tracking. You can temporarily change the branch you are tracking from
main to another test branch using the instructions in the note above. In your PagerDuty account, navigate to the integrated service, click its title and you should see a change event labeled Recent Change in the Recent Activity timeline:
By default, the integration tracks the
master branch. If you would like to track a different branch, or track multiple branches:
- Navigate to the service with the GitHub integration select the Integrations tab click to the right of your GitHub integration.
- Click Edit Integration on the right and enter the name of your preferred branch in the branch field. To track multiple branches, add a space between each branch’s name, for example:
feature-branch-1 feature-branch-2 feature-branch-3.
- Click Save changes.
The GitHub Changes integration supports creating change events with GitHub Actions. To use this feature, follow the Integration Walkthrough above to complete configuration, and use the Integration Key with the PagerDuty Change Events GitHub Action.
Not at this time, but we are interested to learn about what you would like to accomplish, please contact our Support team with your use cases and feedback.
Yes, you can add any number of integrations to a single service, including multiple GitHub integrations.
Not at this time, but we would like to hear your feedback. Please contact our Support team.
Updated about 1 month ago