GitHub will not connect

You came back from GitHub, and Cloud did not connect the installation. Cloud connects one only when every check passes, and it does not say which check failed. These are the usual causes.

The install link expired: a press of Connect or Add account is valid for 15 minutes, so leaving GitHub's install screen open longer than that fails.

The browser came back signed in to a different Cloud account than the one that pressed Connect, or signed out.

The installation is not yours on GitHub. Cloud connects an installation only when the GitHub user who returns from the install screen can see it among their own installations. A request that an organization owner approves later does not come back through your browser, so nothing is connected then. Once the App is installed on the organization, press Add account and finish the round trip as a GitHub user with access to that installation.

Too many attempts: more than 20 returns from GitHub in a minute from one network address are refused.

Press Connect or Add account again and finish on GitHub straight away, in the same browser, signed in to the same Cloud account. If it keeps failing, contact support.

The browser shows a line of raw text, {"error":"GitHub cannot be connected right now."}, instead of GitHub's install screen. The Cahaves GitHub App is not configured on the platform, so no account can connect. Contact support.

The Git repository (GitHub App) form shows this card, with "Cloud reads your repositories through the Cahaves GitHub App, and no account is connected yet.", in place of its fields. Press Go to Git providers, connect an account, then open the form again.

There is no message: Repository lists only what the account has given the App access to, and Cloud keeps each account's list for a while to answer quickly. A list is reused as it is for five minutes. After that the saved list still appears first while Cloud fetches a fresh one behind it, so a repository granted a moment ago can take one more reload to appear.

Check on GitHub that the App's installation includes the repository (all repositories, or the repository among the selected ones). Then wait five minutes and reload the form twice.

Cloud asked GitHub for the account's repositories or a repository's branches, and GitHub did not answer. Wait a minute and open the list again.

The account's installation no longer covers that repository, so Cloud cannot list its branches. Grant the repository to the App on GitHub, or pick a repository from the list.

The Account chosen is not one of your connected GitHub accounts, which happens when the account was disconnected while the form was open. Reload the form and choose an account from Account.

You pressed Disconnect on an account that a service still builds from, and Cloud refused. The confirmation dialog says services "cannot deploy again until a provider with access is connected", but Cloud does not disconnect an account in use.

Move each service to another account on its Source card, or delete the services that use it, then press Disconnect again. Disconnecting in Cloud leaves the App installed on GitHub; remove it there as well if you no longer want Cloud to see the account.