# GitHub Integration

Pull selected **GitHub issues** into a schedule as MNTT actions—a light link between your repo and your focus screen, not a full issue manager. Issues stay in GitHub; MNTT helps you work the next one during the right time block.

## Before you start

You need a GitHub **fine-grained personal access token** with:
- **Issues** — Read and write (on repos you sync)
- **Metadata** — Read-only (for repo listing)

Create one at [github.com/settings/tokens](https://github.com/settings/tokens?type=beta). Copy the token when shown—you will not see it again.

## Add an integration

1. Go to **Setup → Integrations**
2. Add a **GitHub** integration
3. Fill in:
   - **Attach to Schedule** — which time block receives synced issues
   - **Integration name** — label you will recognize
   - **Token**, **organization/username**, and **repository** name
   - **Assigned user** (optional) — sync only issues assigned to that GitHub user
4. Save

## Sync issues

When the integration uses **manual sync**:

1. Land on **Focus** during the attached schedule
2. Click **Sync Active Schedule** (when shown)
3. New and updated issues import as actions; duplicates are skipped

Check the automation indicator beside the button for last sync status. Fix token or permission errors in the integration form if sync fails.

## Working synced actions

Synced tasks show **Synced with** and the integration name in the task list. Complete work in MNTT as you would any action—the issue remains in GitHub for your team; MNTT is your focus queue, not a replacement for GitHub's issue board.

## Use cases

**Side project evenings:** **Side Hustle** schedule + repo sync—Focus shows the next issue during 7–9 pm only.

**Client open source:** One repo per schedule so "who am I working for?" matches the active block color.

**Sprint subset:** Filter by assigned user so only your issues appear, not the whole backlog.

## Tips

- Map **one schedule to one kind of work**—avoid syncing every repo into the same block
- Keep a lean action list; GitHub holds the full backlog
- MNTT is for *now*—sync before a work block, not every five minutes
- See **Action Tips** for backlog vs active-week workflow