How to Connect GitHub to Daily Pick (PAT + Repository Guide)

Published on: October 26, 2025 by Daily Pick

Tags: github, daily pick, integrations, engineering productivity, standups

GitHub already tracks who owns each issue and which pull requests are waiting for review. When you hook GitHub into Daily Pick, the stand-up dock can automatically display collaborators, open issues, and quick links to “Open” so your team never hunts for context. Here’s the full walkthrough.

Requirements

Read access to the repository (private or public).
Permission to create a personal access token (classic or fine-grained).
The repository slug in owner/repo format (e.g., daily-pick/game-hub).

Daily Pick only needs read access. You can keep two-factor auth enabled and still use the integration.

Step 1 — Create a GitHub personal access token

Open github.com/settings/tokens while signed into the correct account.
Choose Fine-grained tokens if available. Otherwise, select Generate new token (classic).
Provide a descriptive name such as Daily Pick Stand-up.
Set an expiration (90 days is a solid default).
Scopes to enable:
- Fine-grained: select the specific repository and grant Metadata + Issues read access.
- Classic: check repo (read) and read:org if you need org-level member data.
Click Generate token and copy the string immediately.

Step 2 — Complete the GitHub card in Daily Pick

Visit Daily Pick Settings → Third-Party Integrations → GitHub.
Enter:
- Repository full name: owner/repository exactly as it appears in the URL.
- Personal access token: the value you just generated.
Decide whether to enable:
- Include assigned work when testing to fetch open issues (default recommended).
- Enable connection to keep the Worker polling.

Step 3 — Test, review, and save

Click Test Connection.
When the Worker responds you’ll see:
- Players detected: collaborators or assignees that Daily Pick can map into the player roster.
- Assigned work: open issues grouped by assignee with quick “Open” links.
Use the action buttons if you want to import players or store the issue snapshot.
Finish by clicking Save Connection so the Worker keeps the token server-side.

Troubleshooting checklist

Message	Likely cause	Fix
`Not Found`	Repository slug typo or missing access	Confirm the `owner/repo` path, and verify the token was granted access to that repo.
`Bad credentials`	Token expired or copied incorrectly	Generate a new PAT and paste it again.
`Issues disabled for this repo`	Some repos turn off GitHub Issues	Re-enable Issues or connect another repo that uses them.
Empty player list	No collaborators are assigned to issues	Assign issues to teammates or use GitHub Projects to create ownership before re-testing.

Best practices after you connect

Rotate tokens when people change roles. Delete the old PAT in GitHub Settings so you know exactly who has access.
Use a shared service account if multiple facilitators manage stand-ups; keep personal accounts for emergency overrides only.
Leverage snapshots. If a deploy freezes mid-sprint, click Save assigned work snapshot so the state is preserved for the retrospective.

With GitHub wired in, Daily Pick becomes your unified view: queue order, notes, and the exact issues each teammate is touching. Revisit the Settings page any time you want to switch repositories or revoke the connection.