File GitHub issues from Session Recorder

Connect a repository once, then file a GitHub issue directly from a finished recording. The issue links to the protected report.

Connect a repository#

1. Complete protected publishing setup. Optionally configure AI summaries to draft the issue automatically.
2. Open Settings → GitHub, select Add repository, and enter owner/repository.
3. Select Create a GitHub token. Choose the correct resource owner and only the repository you want to file into. Give the token Issues: Read and write; GitHub includes the required Metadata access. Choose an expiration and generate the token.
4. Paste the token into that repository’s token field and select Save GitHub settings. The extension checks repository access before saving.

Add a repository for each destination you use. Each repository has its own token, so you can scope each credential to one repository. See GitHub’s issue creation permissions for the API requirements.

To file through the Proofline GitHub App instead of tokens, see Connect Proofline.

File from the report#

1. Stop recording to open the report.
2. Select the arrow beside File issue to choose a configured repository. New reports remember your last choice; existing drafts keep their saved destination.
3. Select File GitHub issue. The extension generates a summary when AI is configured, publishes the protected report, and creates the issue with a link. An existing or edited draft is kept.

A full-page progress screen shows repository verification, summary preparation, publishing and issue creation. Keep the report tab open while filing. When it finishes, View issue opens the created issue.

Cancel stops further work and keeps saved drafts and published reports. It does not undo a completed upload or issue creation. If GitHub may already have received the issue, use Check GitHub issue to find it before retrying.

The summary is visible to everyone who can read the repository; the linked report still requires sign-in. See One-click GitHub issues for what each party can see.

If filing fails#

• 401 or 403: check the token’s expiration, repository selection and Issues permission. An organization may require token approval.
• 404: check the repository spelling and whether the token can access it.
• Uncertain response: use Check GitHub issue before retrying. The extension looks for an accepted request to avoid duplicate issues.
• Publishing error: follow the Cloudflare troubleshooting steps.

The token stays in local extension storage and is excluded from reports and exports. Unpublishing a report does not delete its GitHub issue.