Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How can I allow any user to merge a pull request that contains Git LFS Locked files?

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:

  1. User A creates a new branch, claims a Git LFS Lock on a large binary file
  2. User A performs edits on the binary, does his work, commits, pushes the branch to the server
  3. User A creates a Pull Request
  4. User B (me, or anyone else) cannot merge the PR (the button is grayed out) because of the lock on the binary file, see image below.

 

bitbucket-lfs.png

 

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?

Thanks,

Stephane

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
6.9.0
TAGS
Community showcase
Published in Bitbucket Pipelines

Bitbucket Pipelines Runners is now in open beta

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...

602 views 15 9
Read article

Community Events

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

Events near you