Your Git provider sends a webhook to Bitrise whenever you push code, open a pull request, or push a tag. If a build doesn't start, or starts when you don't expect it to, check the webhook first. Your Git provider keeps a log of every delivery: the payload it sent and the response Bitrise returned.
Check recent webhook deliveries
Open your repository's webhook settings on your Git provider.
Find the Bitrise webhook and open its recent deliveries.
Find the delivery for the push, pull request, or tag that should have triggered a build.
Check whether the delivery succeeded, and read the response from Bitrise.
To test again, redeliver the webhook from the same page.
Your Git provider's webhook docs
GitHub: Testing webhooks
GitLab: Troubleshoot webhooks
Bitbucket: Troubleshoot webhooks
Builds trigger twice on GitHub
If you connect your repository through the GitHub App, the app manages webhooks for you. Remove any webhooks you added manually, or every event triggers two builds.
Still not working?
Check Builds aren't getting triggered and Build Trigger does not work. If the issue persists, enable Support access and contact our Support team.