title: Avoid Using Master Branch for BitBucket Pipeline
body: <p>I'm setting up a CI pipeline on a BitBucket Repository based around docker. I'm running build commands then up then test, basically. This all works so far, but the issue I'm having is BitBucket <strong>only</strong> commits or lets me edit changes to the <em>bitbucket-pipelines.yaml</em> file on the master branch.</p>
  
  <p>I'm not the only developer on the project, and right now our master is our staging/ready for prod branch, and we've all agreed to use other branches for things and let one of us manage master and merges into it.</p>
  
  <p>My question is, can I use another, different branch than master to "manage" my pipelines file on, like our active development branch? For some reason, I can't find a way to add a pipeline to another branch, and pushing up a bitbucket-pipelines.yaml file on the develop branch won't trigger a build.</p>
  
  <p>For reference, my pipeline yaml:</p>
  
  <pre><code>image: atlassian/default-image:2
  
  pipelines:
    # pull-requests:
    #   'feature/*':
    #     - step:
    #       services:
    #         - docker
    branches:
      develop:
        # each step starts a new Docker container with a clone of your repository
        - step:
          services:
            - docker
          script:
            - (cd app/laravel/ ; npm install)
            - (cd app/laravel/ ; npm run production)
            - docker build -t myApp -f app/Dockerfile app/
            - docker stack up -c docker/docker-compose.yaml myApp
  </code></pre>