apperiodocs

GitHub issues

Turn an error into a drafted GitHub issue, and resolve it by closing the issue.

Create an issue from an error

  1. Open the error on the Issues page.
  2. Choose Create GitHub issue. Apperio drafts the title and body; this takes a few seconds.
  3. Read the draft and edit anything you like. The body is GitHub markdown.
  4. Choose Create issue. The issue is opened in your linked repository with the labels bug and apperio, and linked to the error.

From then on the error shows the issue number and whether it is open or closed. Each error links to one GitHub issue: once it is linked, the button becomes Issue # followed by its number, and opens it on GitHub.

What goes in the draft

An AI model writes the draft from the error’s context: the message, the stack trace, how many times it happened and how many sessions it reached, when it was first and last seen, its environments and first release, and any suspect commits. The dialog says Drafted by AI when it did.

If the AI step isn’t available, you get a fixed template with the same facts: a summary, an impact list, the stack trace, possible causes, and a link back to the error in Apperio.

Check what you publish

The draft includes the stack trace and error message as Apperio received them. If your repository is public, so is the issue. Remove anything you wouldn’t want shown before you create it.

Two-way sync

  • Close the issue on GitHub and the error becomes Resolved via GitHub in Apperio, usually within seconds.
  • Reopen the issue and the error goes back to Unresolved.
  • If the error happens again after it was resolved, it is marked Regressed and you are notified. The GitHub issue isn’t reopened for you.

Requirements

  • A linked repository. See Connect GitHub.
  • The GitHub App installed on that repository for the sync. With only a personal token, Apperio can create the issue but never hears that it was closed.
  • The project owner or an admin to create the issue.