Connecting GitHub

DevClocked connects to GitHub through the DevClocked GitHub App using a browser-based authorization flow. There's no Personal Access Token to generate or paste — you authorize in the browser and pick exactly which repositories the App can read. Access is read-only, and credentials refresh server-side so the connection stays healthy over time.

Connecting

1. Go to Settings > Integrations and click "Connect GitHub"
2. Complete GitHub's browser authorization flow
3. Install the DevClocked GitHub App on the account or organization that owns your repositories
4. Choose which repositories to grant access to (all repos, or a specific selection)
5. DevClocked confirms the installation and loads the repos you just granted access to

Installation coverage

Commits only sync for repositories the DevClocked GitHub App is actually installed on. If your GitHub authorization succeeds but the App isn't installed on the account that owns a repo, DevClocked flags it as "needs installation" and that repo won't sync until you install the App there. If you own repos across multiple accounts or orgs, install the App on each one.

Migrating from a Personal Access Token

Older connections that used a Personal Access Token still work read-only, but they're marked "Legacy PAT". Reconnect once through the GitHub App flow to move onto refreshable credentials that recover cleanly when your access changes.