Auto-deploy triggers a new deployment on every push to a target branch. It relies on a webhook installed on your Git repository.
How it works
- When the project is created, Paylood installs a webhook on your repository (GitHub, GitLab or Bitbucket).
- On every
git pushto the project’s branch, the provider calls the Paylood webhook. - Paylood verifies the webhook signature, creates a
queueddeployment and runs the pipeline. - The deployment status is tracked in real time in the application.
Enabling auto-deploy
- Open your project.
- In the Settings tab, enable the Auto-deploy toggle.
- (Optional) select the branch that should trigger deployments.
Capture à venir
en/git-providers-auto-deploy
Cette capture illustrera la vue correspondante. Elle est générée automatiquement par le pipeline Playwright.
Tip
Auto-deploy is enabled by default for the project branch. You can disable it at any time for full manual control.
Branch filtering
Each project environment is tied to a branch. The webhook only triggers a deployment when the push concerns the environment’s branch. Other branches are ignored.
Verify the webhook is installed
On your Git provider, open the repository settings → Webhooks. You should see an entry created by Paylood pointing to https://<your-api-domain>/webhooks/<provider>.
Warning
The webhook must be able to reach your Paylood API from the internet (API_BASE_URL public). It is not installed for local repositories (ZIP) or localhost URLs.
Webhook security
Each provider uses its own verification mechanism:
| Provider | Verification header |
|---|---|
| GitHub | x-hub-signature-256 (HMAC-SHA256) |
| GitLab | x-gitlab-token |
| Bitbucket | x-hub-signature (HMAC) |
A webhook with an invalid signature receives a 401 error and no deployment is created.
Fixing an auto-deploy that does not trigger
- Check that auto-deploy is enabled in the project settings.
- Check that the webhook still exists on the repository (it can be removed on repository transfer).
- Check that the push branch matches the environment’s branch.
- Look at the provider’s Webhooks section for recent deliveries and their HTTP statuses.
After a repository transfer or fork, reinstall the webhook by editing and saving the project configuration.