Skip to main content
Once you’ve installed the AppSignal GitHub integration, given AppSignal permission to read and write issues in your GitHub repositories, and connected your AppSignal app to the desired repo, you can convert AppSignal incidents into GitHub issues. You can also link issues and pull requests that already exist, and follow their status from the incident.

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. Error incident summary page with the Send to GitHub action in the Actions panel This opens a screen that allows you to create a GitHub issue. AppSignal fills in the title and description for you. The description includes a link to the AppSignal incident, the error message, and, when applicable, up to the last 10 lines of the backtrace. You can modify the title and description, but we recommend keeping the incident link and the backtrace. Create GitHub issue screen with a prefilled title and description Select Create GitHub issue to create the issue in the GitHub repo your application’s namespace is connected to. The new issue appears in the Actions panel, and the incident’s logbook records Sent the issue to GitHub. If AppSignal can’t create the issue, the create screen tells you why. Either your app isn’t linked to a GitHub repository yet, or the AppSignal GitHub app has no Issues (write) permission or no access to the repository. To fix either, see Link AppSignal to your app’s repository on GitHub. You can change the repo your AppSignal application’s namespaces are connected to in your AppSignal application’s settings page. You can also manage the access rights of AppSignal in your GitHub integration settings. 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/123 or https://github.com/acme/shop/pull/456.
  • The shorthand acme/shop#123.
AppSignal only links references to repositories of the GitHub organization, or user account, that owns the linked repository. An app linked to 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. Incident summary with a note containing a GitHub issue URL, the Linked #6 on GitHub logbook entry, and the View #6 in GitHub action with an Open badge The AppSignal MCP server links issues the same way when an AI agent writes a note on an incident. To link an incident from GitHub:
  1. Copy the incident’s URL from AppSignal.
  2. Paste it in the description of a GitHub issue or pull request, with a word in front of it. For example: Fixes <incident URL>.
  3. Create the issue or pull request, or save your edit.
The issue or pull request now shows in the incident’s Actions panel and logbook. Capital letters and a colon after the word, such as Fixes:, work too.
An incident's logbook in AppSignal with two entries added from GitHub: one issue referenced and one issue linked, each with a github badge, above an earlier link added from a note

Issues linked and referenced from GitHub, in the incident's logbook.

Good to know:
  • 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#123 references 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.
An incident's Summary tab in AppSignal. The logbook shows AppSignal changed the status of #20 on GitHub from merged to deployed. In the Actions panel, View #20 in GitHub has a Live badge, and a tooltip reads Deployed in 9175503 2 minutes ago

A linked pull request shows Live once a deploy ships it.

When AppSignal creates a deploy marker for a new deploy, it asks GitHub which commits were added since the previous deploy in the same namespace. If a linked pull request was merged in one of those commits, it changes to Live. For a pull request to show Live, you need:
  1. 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 as See acme/shop#123, stays Merged.
  2. Your app linked to the pull request’s repository. See Link AppSignal to your app’s repository on GitHub.
  3. 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.
  4. 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.
AppSignal doesn’t track:
  • 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.3 when the tag is v1.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.
To have AppSignal close an incident when its fix ships:
  1. 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.
  2. Merge the pull request.
  3. Deploy it. AppSignal needs to see the deploy, so the pull request changes to Live.
AppSignal then closes the incident. The logbook records the change to Closed with a deploy badge, and names the pull request. Good to remember:
  • 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 as See before 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.
The incident is now the one place to check on a fix: which issues and pull requests belong to it, and whether each is open, merged, closed, or live. To jump from a backtrace line to the code that shipped, set up backtrace links next.
🛟 If you are having trouble making GitHub issues for AppSignal incidents, please get in touch, and we’ll help you further.