GitHub Issues Notifications

Automatically create GitHub Issues when incidents occur, and add comments + close them upon recovery.

1. Log in to GitHub

   Log in to GitHub.

2. Create a Fine-grained Personal Access Token

   Go to Settings > Developer settings > Personal access tokens > Fine-grained tokens and click “Generate new token”.

3. Set permissions

   • Repository access: Select the repository where you want to create Issues
   • Permissions > Repository permissions > Issues: Read and write

   The token owner must also have access to that repository. If organization policy requires approval, complete approval before using the token.

4. Copy the token

   Copy the token that starts with github_pat_.

1. In the dashboard, open Settings > Integrations, then select Configure for GitHub
2. Enter a recognizable Name
3. Enter the following:
   • Token: Personal Access Token
   • Owner: Repository owner (username or organization name)
   • Repo: Repository name
   • Labels (optional): Labels to add to Issues (e.g., incident, manako)
4. Select Add

Manako remembers the Issue number created for each incident and automatically closes it upon recovery.

The created Issue number is stored per channel for 90 days. On recovery, Manako attempts to add a resolution comment, then closes the Issue with the completed reason. A comment failure does not block the close operation.

When an incident occurs:

## Incident Details

- **Monitor**: API Health
- **Monitor ID**: 01JABC...
- **URL**: https://example.com/health
- **Incident ID**: 01JXYZ...
- **Detected at**: 2026-03-26T12:00:00Z

---

_Auto-created by Manako monitoring_

• Test fails: Test does not create an Issue; it only checks whether the Token can fetch Owner/Repository. Check repository selection, token expiry, organization approval, and the token owner’s repository access.
• Normal delivery cannot create an Issue: The API fails if Issues are disabled for the repository. If Labels are configured, ensure the token owner can apply them.
• The Issue is not closed after recovery: Auto-close cannot run if the Issue-number mapping failed to save, expired after 90 days, or cannot be found during recovery.
• There is no maintenance notification: The GitHub integration intentionally skips maintenance start and end events.
• Test succeeds but normal notifications do not: Check monitor-specific channel links. If links exist but all are disabled, Manako does not fall back to team-wide channels.
• Notifications stop during rapid state changes: After more than three state changes for the same monitor within 10 minutes, the flap guard suppresses subsequent notifications.
• Notifications appear duplicated: A sent retry for the same incident, channel, and event type is skipped; failed or pending sends are retried.

After Test succeeds, the channel has a 60-second cooldown. A failure on one GitHub channel does not stop the remaining channels.