Deploy on push
With deploy on push, a git push to a branch deploys the environments of the project that follow that branch and have it switched on.
It takes three steps: make the webhook in WSLA, add it at your Git host, switch it on per environment. Setting it up needs an owner or admin.
1. Make the webhook
Section titled “1. Make the webhook”- Open the project and its Deploy on push tab.
- Press Set up deploy on push.
- Copy the address and the secret. The secret is shown only now.
2. Add it at your Git host
Section titled “2. Add it at your Git host”GitHub: the repository’s Settings → Webhooks → Add webhook.
- Payload URL: the address.
- Content type:
application/json. - Secret: the secret.
- Just the push event.
GitLab: Webhooks, the address as URL and the secret as Secret token, push events.
Gitea: Webhooks, the address and the secret as Secret.
3. Switch it on for an environment
Section titled “3. Switch it on for an environment”- Open the environment and its Advanced tab.
- Under Deploy on push, switch on Deploy when its branch gets a push.
The project’s Deploy on push tab lists its environments and says for each whether it deploys on a push, and to which branch.
See what arrived
Section titled “See what arrived”Last deliveries on the project’s Deploy on push tab lists the Git host’s calls with what each one started: a deploy per environment, or the reason one was skipped. Deliveries are kept for 30 days.
New secret, or switch it off
Section titled “New secret, or switch it off”- New secret makes a new one. Put it into the webhook at your Git host, or its calls are refused.
- Switch off stops deploying on a push for the whole project.

