GitHub
Monitor pull requests, CI failures, and issue assignments across your repositories. Get notified when something needs your review or attention.
Quick Setup
- Go to github.com/settings/tokens
- Click Generate new token (classic) or Fine-grained token
- Give it a name like "Phyllax" and select the scopes you need (at minimum:
repo,notifications,read:org) - Click Generate token and copy the token (starts with
ghp_) - In Phyllax → Integrations → GitHub → Connect → paste the token
Required Credentials
| Field | Where to find it |
|---|---|
| Personal Access Token | github.com → Settings → Developer settings → Personal access tokens (ghp_...) |
Classic vs Fine-grained tokens
Classic tokens (starting with ghp_) are simpler to set up. Fine-grained tokens give more granular control but require selecting specific repositories. For most users, a classic token with repo and notifications scopes is the easiest option.
What Phyllax Monitors
| Schedule | What it checks |
|---|---|
| PRs needing review | Pull requests assigned to you or requesting your review |
| Failing CI checks | CI/CD pipeline failures on your repositories or PRs |
| New issues assigned | New issues assigned to you |
| Stale PRs | Pull requests open more than 2 days with no review activity |
Notification Actions
When GitHub finds something important, the notification card shows:
- View issue / View PR — open the issue or pull request in your browser
- Add comment — AI drafts a comment you can edit before posting
- Assign to me — assign the issue or PR to yourself
- Escalate — flag the item for team leads
- Mark complete — close the issue or merge the PR
All action chips that involve writing (Add comment, Escalate, etc.) open the AI draft panel — AI generates a suggested response that you can edit before posting.
Troubleshooting
"Bad credentials" error
Your personal access token is invalid or expired. Go to github.com → Settings → Developer settings → Personal access tokens and generate a new one.
Can't see private repositories
Make sure your token has the repo scope, which grants access to private repositories. Fine-grained tokens need explicit repository access granted.
CI check results not showing
The token needs repo scope to access check runs and statuses. If you're using a fine-grained token, enable the "Checks" permission.