Skip to main content
Setup time: 5 Min
Effortlessly connect GitHub with All Quiet for streamlined incident management.
The first part of this documentation focuses on creating the integration. The second explains how to create GitHub issues based on All Quiet incidents (Outbound). Want to create new incidents from GitHub (Inbound)? Follow the third part of this guideline.
Currently, you can only install one All Quiet integration per GitHub workspace/organization. Choose your All Quiet Root Team and the GitHub repository access wisely, as these determine where incidents are created and where issues are synced. Need multiple integrations? Contact support@allquiet.app

​
Create Outbound Integration

  1. Click on the Outbound Integrations tab.
  2. Click on + Create.
  1. Enter a Display Name for your integration, e.g. “GitHub”.
  2. Select a Root Team.
    For Organizations with Pro and Enterprise plan: This is going to be the root team of your integration. You will be able to add additional teams in the next step.
  3. Select GitHub as the integration’s type.
  4. Forwarding settings:
    1. Default: Always After Forwarding - GitHub issues will only be created if users manually forward specific incidents or if you set up advanced routing rules for your GitHub integration that automatically forward incidents in specific scenarios.
    2. Alternative: Always will automatically forward all incidents to GitHub and create issues, unless excluded by additional advanced routing rules.
      You can change your selection anytime.
  5. Click Create Outbound Integration.

​
Add All Quiet to GitHub

Once you’ve successfully created your new outbound integration, you’ll be redirected to its Settings page.
  1. Observe that the installation status of the All Quiet integration is still pending.
  2. Click Install on GitHub to authenticate the integration. Make sure you have the necessary GitHub permissions to install the app on the desired repositories.
In the Edit tab, you can change general settings like the integration’s Forwarding settings.
Only for Pro and Enterprise plan - Manage your Team Connections: The root team is pre-selected, and you can add the integration to further teams within the root team’s organization. Team Administrators can add / remove those teams they are an Administrator in, Organization Administrators & Organization Owners can manage the connections to all teams of the organization.

​
Configure Outbound Integration

After granting All Quiet the required access to the desired repositories of your Organization, you are redirected back to your GitHub integration’s details page in All Quiet. Next, configure the integration:
  1. Select the GitHub organization and repository you want to create issues in.
  2. Configure how new GitHub issues should be created and All Quiet actions should be synced to the GitHub issue.
    • The Initial State for new issues created from All Quiet incidents.
    • Optional: Add labels to new issues created from All Quiet incidents.
    • The GitHub issue status when an incident is resolved.
    • The GitHub issue status when an incident is reopened.
    • Optionally, you can post incident activity as a comment in the GitHub issue.
  3. Optionally, configure updates on GitHub issues that sync to All Quiet incidents.
    • GitHub states that resolve incidents in All Quiet.
    • GitHub states that reopen incidents in All Quiet.
  4. Make sure to Save your settings.
If you decide to save & stop here, your GitHub Outbound Integration with All Quiet is ready to go. Depending on your setup, All Quiet incidents will now automatically create issues in GitHub or can be forwarded manually to GitHub. The states will be synced based on your selection.

​
Create All Quiet Incidents From GitHub

This feature is basically the GitHub inbound integration. You can create All Quiet incidents from GitHub issues. Here’s how it works:
If you use both inbound and outbound, avoid creating multiple GitHub inbound configurations that point to the same GitHub repository. Otherwise, an outbound-created issue can trigger another inbound configuration and accidentally create duplicate incidents or loops. We recommend using only one inbound integration per GitHub repository.
For Pro and Enterprise plan users: No matter which teams you added in Team Connections when setting up the outbound integration, all All Quiet incidents will always be created in the integration’s root team.
On your GitHub outbound integration’s details page in All Quiet, scroll below section Create incidents From GitHub To create incidents from GitHub:
  1. Activate Create on new issue and / or Create on issue update. Otherwise, GitHub issues will not create new All Quiet incidents at all.
    • Enable Create on new issue: All Quiet incidents will be created when creating a GitHub issue matching the criteria below.
    • Enable Create on issue update: All Quiet incidents will be created when updating an existing GitHub issue to match the criteria below.
  2. Optionally, restrict All Quiet incident creation to GitHub issues that match specific criteria (for example labels and states), depending on your setup.
  3. Save GitHub Settings.
You have successfully enabled the GitHub inbound integration. To manage your settings, open your GitHub integration details page.