Create a GitHub issue from an incident
Open the relevant namespace for your AppSignal application, select Errors in the side navigation, and then Issue list. Open the error incident you want to send to GitHub. On the incident’s Summary tab, select Send to GitHub in the Actions panel.

Link an existing issue or pull request
Often the fix is already underway: someone opened a pull request, or the bug has a GitHub issue. Drop its link in a note, and AppSignal tracks it for you. The incident shows where the fix stands, and nobody has to ask whether it shipped. Open the incident’s Summary tab, write a note in the Logbook box with the GitHub issue URL, and select Post note. AppSignal recognizes two forms of reference anywhere in the note:- A full URL, such as
https://github.com/acme/shop/issues/123orhttps://github.com/acme/shop/pull/456. - The shorthand
acme/shop#123.
acme/shop also links references to acme/shop-api, but ignores references to other organizations. An issue that is already linked is not linked again, so editing the note does not create duplicates.
The logbook records Linked #123 on GitHub, with the number linking to the issue. The issue also appears in the Actions panel with its status.

Link an incident from GitHub issues and pull requests
To link an incident from GitHub:- Copy the incident’s URL from AppSignal.
- Paste it in the description of a GitHub issue or pull request, with a word in front of it. For example:
Fixes <incident URL>. - Create the issue or pull request, or save your edit.
Capital letters and a colon after the word, such as
Fixes:, work too.

Issues linked and referenced from GitHub, in the incident's logbook.
- The issue or pull request must be in a repository of the same GitHub organization, or user account, as the repository connected to your app.
- Removing the URL from the description doesn’t remove the link from the incident.
- The logbook shows who added the link on GitHub.
- The same words work in notes on the incident. For example,
See acme/shop#123references the issue.
Follow linked issues from the incident
The Actions panel shows a button for every linked issue and pull request, labeled View #123 in GitHub. The buttons appear in the order the issues were linked. Hover over a button to see when the issue was linked or referenced. Select it to open the issue on GitHub, or to re-create the issue. Re-creating removes the link and opens the create screen again. Each button shows the issue’s status as a badge: Open, Closed, or, for pull requests, Merged or Live. AppSignal reads the status when you link an issue. It updates the status when the issue or pull request is closed, reopened, or merged on GitHub. Every status change also shows in the incident’s logbook, for example Changed the status of #123 on GitHub from open → merged. The entry shows who made the change on GitHub. If that person is a member of your AppSignal app and has linked their GitHub account, the entry shows their AppSignal name. Status updates need the Issues and Pull requests permissions of the AppSignal GitHub app. When AppSignal asks for them, an owner of your GitHub organization has to approve the new permissions on GitHub. Without them, linking still works, but linked issues show no status badge.See when a linked pull request is deployed
Once a deploy ships a linked pull request, its badge changes from Merged to Live. Hover over the button to see the deploy’s revision and when it happened, for example Deployed in 9175503 2 minutes ago. The logbook records the change as Changed the status of #20 on GitHub from merged → deployed, made by AppSignal.
A linked pull request shows Live once a deploy ships it.
- A link, not a reference. Put a linking word, such as
Fixes, or no word in front of the link, on GitHub or in a note on the incident. A referenced pull request, such asSee acme/shop#123, stays Merged. - Your app linked to the pull request’s repository. See Link AppSignal to your app’s repository on GitHub.
- A deploy marker for each deploy, with a revision GitHub knows: a commit SHA, a tag, or a branch name. See Choosing a revision value.
- The Contents, Issues, and Pull requests permissions on the AppSignal GitHub app. When AppSignal asks for new permissions, an owner of your GitHub organization has to approve them on GitHub.
- A pull request you link after the deploy that shipped it.
- A deploy of more than 1,000 commits.
- A revision GitHub doesn’t know, such as a build number, or
1.2.3when the tag isv1.2.3. - Rollbacks. A pull request stays Live after you roll back the deploy that shipped it.
- The exact commit of a branch deploy. If the revision is a branch name, AppSignal uses the branch’s latest commit when it checks. That commit can be newer than the one you deployed.
- The same deploy twice. If one deploy has a deploy marker in several namespaces, the pull request changes to Live only once.
- A deploy GitHub can’t compare. If GitHub returns an error, the pull request stays Merged, and AppSignal doesn’t show the error.
- A failed logbook entry. If saving it fails after the pull request changes to Live, AppSignal doesn’t retry it.
Close the incident when its fix is deployed
This feature is in beta, as part of AppSignal Labs. Ask
Support to turn it on for your organization.
- In the pull request’s description on GitHub, write
Fixes <incident URL>. You can also post the pull request’s URL in a note on the incident. - Merge the pull request.
- Deploy it. AppSignal needs to see the deploy, so the pull request changes to Live.
- The incident needs to be open. Its state needs to be Open or Work in progress.
- Link the pull request, don’t reference it. Paste the incident’s URL in the pull request’s description, or the pull request’s URL in a note on the incident. Put
Fixes, or no word, before the URL. A word such asSeebefore the URL only references it, and a reference never closes the incident. - AppSignal waits for every merged pull request. If the incident has more than one, AppSignal closes it once the last one is Live. Linked issues, and pull requests that aren’t merged yet, don’t keep it open.
- Errors from the old code don’t reopen it. While a deploy rolls out, hosts that still run an older deploy can report the error. Those errors count toward the incident, but don’t reopen it or send notifications. An error from the new deploy, or a later one, reopens it as usual.
- Your changes come first. If you reopen the incident, deploying the same revision again doesn’t close it. Once the incident’s state changes again, errors from older deploys can reopen it, like any other error.
🛟 If you are having trouble making GitHub issues for AppSignal incidents,
please get in touch, and we’ll help you
further.