Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
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

Hello Team,

  • A Jira issue is assigned to XYZ (= developer)
  • XYZ does the required development on a specific Bitbucket branch
  • After finishing the development, XYZ creates a pull request on Bitbucket
  • The reviewers (= most of the time ABC or PQR) review the code changes and provided some feedback
  • After approving the pull request the reviewer merges the pull request
  • The BitBucket uses the name of the reviewer as the author of the commit.

This last step is where my issue is situated. I would like to see that the author of the commit remains 'XYZ' as he/she did the code changes and not the name of the person that did the merge.

Anybody has come across this or any suggestions which will help me to get this done using any add-on or scripting would be appreciated.

 

Thanks,

1 answer

Hi @Yogesh Mude ,

You are probably using 'Merge commit --no-ff' as your merge strategy. Then the person who is merging will always create a merge commit and therefore is the author of the commit. If you don't want that you can either let the person who created the pull request merge the pull request. Or you can another merge strategy (e.g. fast-forward). 

Note that the first solution a process change (the developer stays responsible for getting his /her changes into the main branch) and the second is a change in the workflow, the developer needs to date with the main branch in order to fast-forward).

 

Rudy

Hi Rudy,

Thanks for the suggestions.

If possible, can you please elaborate a little bit more on fast-forward..the developer needs to date with the main branch in order to fast-forward).

Thanks,

Yogesh

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bitbucket

Calling any interview participants for Bitbucket Data Center

Hi everyone,  We are looking to learn more about development teams’ workflows and pain points, especially around DevOps, integrations, administration, scale, security, and the related challeng...

505 views 6 4
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