Troubleshooting
A push did not deploy
Why a push to GitHub left no deployment behind, checked setting by setting.
Updated
A service built from GitHub deploys when a push reaches its branch, and each such deployment is listed on the service's Deployments tab with the trigger Git push. When a push leaves no row there, Cloud either decided the push was not for this service or dropped it. Neither shows a message, so check the causes below in order.
Check the service's source
Open the service's Overview and read its Source card.
| What you find | Why the push did not deploy | What to do |
|---|---|---|
| Deploy on reads Only when I ask | The service deploys only when you press Deploy. | Press Deploy, or set Deploy on to Every push and press Save source. |
| Watch paths lists directories | A push deploys only when it changed a file under one of them. A push that touched nothing there is skipped on purpose. | Check the files the push changed. Leave Watch paths empty to deploy on every push to the branch. |
| Branch is not the one you pushed to | Only a push to the service's own branch deploys it. A tag, or deleting a branch, never deploys. | Push to that branch, or choose the right one under Branch and press Save source. |
| Repository or Account is not the one you pushed to | Cloud matches a push by the GitHub account connection, the repository and the branch together. | Choose the right account and repository and press Save source. |
A push of 20 commits or more is always deployed, whatever the watch paths say, because GitHub then stops listing every file the push changed.
Check what else was happening
A push that arrives while Cloud cannot deploy the service is dropped, not queued. Once the cause is cleared, the next push deploys again; to deploy the commit you already pushed, press Deploy.
| Situation at the moment of the push | What to do |
|---|---|
| A deployment of the service was already running | Wait for it to finish, then press Deploy or push again. |
| The account was suspended | Contact support to have the suspension lifted. Then press Deploy. |
| Paid work was refused, for a missing card, an unpaid month or the monthly limit | Clear the cause on Billing, then press Deploy. |
| A backup of the service was running, or a volume attachment was awaiting confirmation | See Deploy is greyed out or refused, then press Deploy. |
| Your workspace was still being prepared | See Your workspace is still being prepared. |
Check GitHub's side
GitHub sends a push to Cloud only for repositories the Cahaves GitHub App can see. If the repository was removed from the App's selected repositories, or the App was uninstalled, no push arrives, and the next Deploy fails with "Cloud could not reach this repository on GitHub. Check the GitHub App can still see it, then deploy again." Grant the repository to the App again on GitHub: see GitHub will not connect.
For how the branch, the trigger and watch paths work, see Source and deploy on push.