Is there a way to lock down modification of bitbucket-pipelines.yml file?
For example, if we want to run the CI and push changes to servers only on merge to master or develop branch, we could target those specific branches in the pipeline.
But nothing really prevents a develop from creating a branch, modifying the pipeline definition to target their own branch, pushing that new branch - and yay (!) we are running some rogue code on test or prod...
