Skip to guide
Help center

Deploy each push to GitHub

Turn on deploy on push for an application built from a GitHub repository, follow each deployment beside its commit, and know what happens to pushes during a deployment.

What deploy on push does

With Deploy on push, a commit pushed to GitHub deploys the application that builds from that repository. It deploys the pushed commit, with the build settings and variables the application has at that moment.

The application deploys pushes to the branch it follows: the revision of its build source, or the default branch of the repository when that revision is empty. A push to another branch, or a tag, deploys nothing.

GitHub shows how each deployment goes beside its commit, with a link to the application in Tenkai.

Turn on deploy on push

Owners, admins and developers turn it on.

  1. Connect the GitHub account of the repository to your team, from the team settings. See Connect GitHub.
  2. Open the application, then its Configuration tab.
  3. Under Deploy on push, turn the switch on.

Pushes deploy as you. If you can no longer deploy, pushes stop deploying until someone who can deploy turns the switch off and on again. If you leave the team, deploy on push turns off.

If your pipeline already calls the deploy hook after its tests, leave deploy on push off: each push would deploy twice, once before the tests pass.

Pushes during a deployment

An application deploys one commit at a time. A commit pushed during a deployment waits, and deploys once that deployment ends. When several commits are pushed meanwhile, only the last one deploys. The others show no status on GitHub.

When GitHub shows no status

GitHub shows the status of a deployment once the account that installed the Tenkai GitHub App accepted its permission to write commit statuses. GitHub asks the account owner to accept it, in the settings of the installation. The deployments still run without it.

When a push deploys nothing

  • Check that the switch is on, and that the branch you pushed is the one the application follows.
  • Check that your team connected the GitHub account that owns the repository, and that its installation reads that repository.
  • A status beside the commit says why Tenkai refused the deployment, such as a backup that runs. Deploy from Tenkai once the cause is gone.