GitHub integration
The GitHub integration for screen recordings lets Vidmatic open an issue for you when you stop a recording. Your coding agent has its own path, covered in recording to issue.
Before you start
You need permission to install a GitHub App on the repositories you want to use.
Connect the GitHub integration for screen recordings
- Go to Settings → GitHub and press Connect GitHub. If Vidmatic is not installed on your GitHub account yet, press Install on GitHub first.
- On GitHub, pick the repositories Vidmatic may open issues in.
- Back in Vidmatic, choose a default repository. Add the ones you use most under Pinned Repositories.
Open an issue when you stop recording
In the recorder, turn on Auto-create GitHub issue. Choose labels and assignees, or keep your repository's defaults; Vidmatic remembers your last choice. Then choose what the issue includes: Link to recording, Full transcription, or both.
When you stop, Vidmatic opens the issue in your default repository. The link it adds is a share link, so anyone who can read the issue can watch the recording (see sharing).
Defaults for each repository
Settings → GitHub keeps your defaults per repository. Default Repository is where new issues go. Default labels are added to every issue Vidmatic opens there; with none set, the issue-type defaults (bug, enhancement) apply instead. Default assignees are assigned to every issue Vidmatic opens there; with none set, issues land unassigned.
Disconnect GitHub
Choose Disconnect in Settings → GitHub. This signs Vidmatic out of GitHub and clears your default and pinned repositories. It does not uninstall the Vidmatic app from your GitHub account; you manage that on GitHub.
Your agent and GitHub
This integration is separate from your coding agent, and your agent does not need it. When your agent files an issue with workstream_from_video for a recording you own, and GitHub is connected here with a default repository that matches the one your agent is working in, Vidmatic files the issue through this integration. Otherwise your agent files it with the GitHub access it already has on your machine.