Prevent pipelines configuration file to be merged

[Weimar_Coro]

Is there a way to prevent the branch specific pipelines configuration files to be merged when using the "Merge" feature on bitbucket?

For example: 

I have my development pipeline configuration to run on any push done to development branch. However, when I merge development to beta branch, the configuration for development branch (pipeline) is also merged which is not the desired behavior.

[joshuatroy · Accepted solution]

Not sure if this helps Weimar:

pipelines:

  branches: 

    dev: 
      - step:
        name: only run when pushed to dev
        script: 
          - pwd

    pipeline: 
      - step:
        name: only run when pushed to pipeline
        script: 
          - pwd

(the spacing is likely off in this yaml snippet^ I just typed it in this text box)

You can specify multiple branches within your pipeline so that step will only run if pushed to that specific branch. Rather than having to worry about merging two different bitbucket-pipelines.yml file you can have the same one on both branches.

[Weimar_Coro]

Good answers. I will try that. Thanks so much!