GitHub

Turn a report into a GitHub issue in one of your repositories.

Turns a report into a GitHub issue in one of your repositories.

Connect it

  1. Settings → Integrations → GitHub.
  2. Enter a personal access token with access to the repository (Contents and Issues permissions). A fine-grained token scoped to just that repo works.
  3. Enter the repository (owner/repo).
  4. Optionally set default labels — bug is applied if you leave it blank.
  5. Test connection.

Filing

Create a → GitHub issue, from the capture editor or a filed report. The created issue carries the title, description, severity/priority/environment, and a link back to the full report.

Screenshots are committed into the repository, not linked from BugCapture's storage — the token needs Contents permission for this. If the token doesn't have it, or the upload fails for any reason, the issue still files, with the screenshot linked from BugCapture's storage instead.

The report gets a GitHub reference (#142) linking straight to the created issue.

One repository per person

Like the other trackers, GitHub is configured once per person. If you file bugs against more than one repository, switching the configured repo in Settings changes where the next issue goes — there's no per-bug repo picker today.

PreviousJiraNextLinear