I have connected our bitbucket repository with the Acquia pipeline following Connecting pipelines to your Bitbucket repo.
I cloned the dev branch of our repo to local and checked out a new branch (dev-deeplink) out of it. After completing the feature, I push this branch to our Bitbucket repository create a pull request.
I have configured our webhook to trigger the pipeline on push event. So now the pipeline will start; if all the jobs run without any error, it will create a build artifact to pipelines-build-dev-deeplink and will push thus to acquia git.
Once the pull request is merged, the pipeline will again run; this time, it will create a build artifact on pipelines-build-dev. So I have two branches pipelines-build-dev-deeplink and pipelines-build-dev.
Is there any way to restrict the pipeline to deploy build artifact on feature branch push?
I want the pipeline to run on feature branch push, but we don’t want the pipeline to push that feature branch to Acquia git as pipelines-build-feature-branch-name. We the want pipeline to push the build artifact whenever we merge it to the dev branch.
Can I achieve it, or is it an expected behavior?