GitHub Issues Notifications

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

Prerequisites: Obtaining a Personal Access Token

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

4. Copy the token

   Copy the token that starts with github_pat_.

Caution

If using a Classic PAT (ghp_), the repo scope is required, but it includes access to all repositories. Fine-grained PAT is recommended.

Manako Configuration

1. Open the “Notification Channels” menu in the dashboard
2. Click “Add Channel” and select GitHub as the Type
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. Click “Add Channel”

Behavior

Manako Event	GitHub Action
Incident Created	Issue creation (title, details, labels)
Incident Recovered	Comment added to Issue + close
Web Change Detected	Issue creation (change diff included in body)

Issue to Incident Mapping

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

Note

If you have configured multiple GitHub channels (different repositories), Issues will be created in each repository and closed individually.

Issue Example

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*