GitHub access
“Reconnect GitHub”, “can't reach your private repository”, and repositories missing from the list.
Reconnect GitHub
What you see
Deploys stop with “DockHosting can't reach your private repository: reconnect GitHub in Settings”, and the dashboard shows a Reconnect GitHub banner.
Why
GitHub no longer accepts DockHosting's access: you revoked it, changed which repositories it may read, or the access came from the old DockHosting platform and has expired.
Fix
1. Open Settings → GitHub in the dashboard and press Reconnect GitHub.
2. On GitHub, approve DockHosting and make sure the repository is in the list it can read. You need admin access to the repository.
3. Open your project and press Redeploy.
My repository isn't in the list
What you see
The repository doesn't appear when creating a project.
Why
DockHosting was given access to some of your repositories only, or the repository belongs to an organization that hasn't allowed DockHosting.
Fix
Reconnect GitHub and add the repository. For an organization's repository, an owner of the organization may need to approve DockHosting on GitHub.
GitHub is slow
What you see
Checking the repository takes long, or says GitHub didn't answer.
Why
GitHub rate-limits or is having an incident.
Fix
Pick your stack by hand on the same screen and carry on: you never have to wait for the check. Or try again in a minute.
No GitHub at all?
Deploy your folder with the dock CLI: dock deploy uploads it, no Git needed.
