Hi there. I have three branches on my bitbucket repo, master, staging and develop. I only want my workflow to run when a pull request is merged in to my staging branch. Previously bitrise would trigger on pushes to develop, staging, all sorts, which I didnât want as every little commit would use up one of my monthly builds.
I only have âPull request: mergedâ ticked in my bitbucket outgoing webhook. I do this because I only allow commits and pushes to develop; master and staging may only have a pull request merged in from the bitbucket web interface.
So, the thing about Pull Request merges is that it is actuall a change (git push) on the target branch. When you merge the PR that generates a new commit on the PRâs target branch, and this is handled as a Git Push on bitrise.io / in the Trigger Map.
What you want for the use case you described is:
Enable the Repository -> Push option of the Bitbucket Webhook
Limit what kind of pushes to build using the Trigger Map on bitrise.io
@viktorbenei i have same problem, but have error in Bitrise server standalone, not cloud (stash):
{âerrorâ:âFailed to transform the webhook: Issue with Headers: No Content-Type Header foundâ}