bitbucket-pipelines, pull-request vs merge

Question

I am trying to use bitbucket-pipelines to test and in a separate step deploy,

When a pull-request is created I want to run unit tests. I see that I can do this with the pull-requests feature.

When the code is merged, I want to create a zip and deploy (copy) code to s3

How do I trigger a step when the code is merged?  Not when the pull-request is created.

Do I need to use tags?

kr_rohit · Answer

@Philip Hodder, any workaround to achieve this?

Darius Bogdan_o9obkj · Answer

@Max DeCurtins I am looking to do a flow similar to the one described by you. Did you find any solution?

Max DeCurtins · Answer

@Philip Hodder The branch pipeline on `master` isn't really a solution for us, because we can't just run the pipeline willy-nilly on any commit to `master`; we need to know something about how that commit originated. Consider:

When a PR from a `release/*` branch is merged into `master`, I would like to run an action that:

* Deletes the `release/release-{#}` branch (yes, I know PRs offer the option to close the source branch on merge, but I don't want to leave that up to a human to remember to check that option)
* Increments a repository variable representing the release number,
* Creates a new `release/release-{#}` branch

I can't hook this action to any commit to `master`, because a hotfix could come in that gets deployed to `master`, and I wouldn't want that change to trigger the release branch-related workflow.

Any suggestions?

Thanks