GitHub Issues
A ticket in one repository when a monitor goes Down. Basic and Pro.
GitHub Issues is a ticket, not a chat. Connect one repository on Account, then enable GitHub Issues on each monitor you want ticketed.
- Down opens one Issue, labeled
gonewatch. The body includes the monitor name, schedule, last heartbeat, and a link to the dashboard. Payload charts stay on the monitor page — they are not copied into the Issue. - Reminders comment on that Issue. If you closed it while the monitor is still Down, Gonewatch reopens it and comments.
- Recovery comments that the monitor is Up, closes the Issue, and stops tracking it. The next Down opens a new Issue.
Not the heartbeat Action
Opening tickets uses the Gonewatch GitHub App from Account. That is separate from gonewatch/heartbeat@v1, which POSTs a heartbeat when a workflow succeeds.
Connect GitHub
- Open Account and choose Connect GitHub.
- Install the Gonewatch GitHub App and grant it one repository. The app needs Issues write and Metadata read — it does not read your code.
- Back on Account, pick that repository if more than one is available.
- Use Check connection to confirm the app can reach the repo. That check does not open a test Issue.
- Edit each monitor and enable GitHub Issues. Connecting does not turn it on for monitors you already created.
One repository per Gonewatch account. Reconnect if you need a different repo. GitHub itself does not email you when Gonewatch opens an Issue — watch the repo or enable GitHub notifications if you want inbox copies.
Disconnect
Disconnect on Account uninstalls the GitHub App and removes GitHub Issues from every monitor. Email is turned back on for those monitors if it was the only remaining destination. Open Issues already created stay in the repo until you close them.