We have just recently enabled Git LFS for our repo, and it's mostly great except we've encountered the following workflow problem when trying to merge PRs on BitBucket:
This merge prevention doesn't make any sense, because the file is locked by the user that performed the changes (which is exactly as it should be). The person pressing the merge button is just confirming the changes are good, not editing the locked file.
Our current workaround is that we ask the PR creator to go and merge his own PR, but this feels unnecessary and would be ideal for us if anyone could merge the PR, for example, the QA tester as soon as he has approved the PR.
I would expect this to be default behaviour, or at least be a Merge Checks setting that we can turn off.
Is there a better way? Can we somehow allow anyone to merge such PRs?
We are excited to announce the open beta program for self-hosted runners. Bitbucket Pipelines Runners is available to everyone. Please try it and let us know your feedback. If you have any issue...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events