Our SCM is BitBucket/GIT and normally it does not allow Pushes to Master, have to Push to a branch and then do a PR to merge to Master. However this doesn't work with the maven release plugin so we have to turn off the PR requirement when performing releases.
What are the best practices for managing this? We would like to avoid having to manually turn something off and then back on again. Is there a way the plugin can manage this? Is there a different release plugin that can handle the PR process? Does anyone know if the BitBucket PR process can be bypassed for certain users using the maven release plugin? That might be the simplest solution if that is possible. -Dave
