- 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 timelines during incident triage or hypercare. They can also see recent changes on incidents of that service, and navigate across all changes in a comprehensive list of Recent Changes across all services.
- 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 changes. They will not generate alerts, incidents or notifications.
In PagerDuty: This integration requires a Manager base role or higher to configure.
In GitHub: This integration requires an Admin role to configure.
We recommend mapping your GitHub events to the PagerDuty service that represents what you are changing. This will make it easy for responders to quickly identify recent changes on their service when they get notified for an incident.
- In your PagerDuty account, navigate to Services Service Directory and click the name of your preferred service. Select the Integrations tab and click Add a new integration.
- Enter an Integration Name in the format
Service-Name-GitHub-Changesand select GitHub Changes from the Integration Type dropdown. Click Add Integration.
- On the next screen in the Integrations list, click the Name of your GitHub Changes integration to view the details screen.
On this screen you will see that the default branch to track will be set to
master, if you would like to change the branch, you may optionally click Edit Integration on the right and enter the name of your preferred branch in the branch field. Click Save Changes
- Next, copy the Integration URL which will be in the following format:
Keep the URL in a safe place as it will be used in later steps.
- 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 was generated in PagerDuty (above) in the Payload URL field, and in the Content Type dropdown, select
x-www-form-urlencoded. 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.
The push event is also supported, but shows less information in PagerDuty. The pull request event is recommended if you use GitHub's pull request functionality. Selecting both pull request and push events may result in two change events for a single action. Please select only one.
- 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
mainto 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 as RECENT CHANGE in grey in the Recent Activity timeline:
Please read our Change Events article for more information on how to send change events and view them within individual services, incidents and across all services in the Service Directory.
The GitHub Changes integration supports creating change events with GitHub Actions. To use this feature, follow the Integration Walkthrough above to complete configuration, and then 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 6 months ago