The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
When a pull request is opened and an other branch is pulled on the branch related to the pull request, the merge commit is included to the "Changes since you last reviewed".
Is it possible to ignore the merge commits in the review or must I use an other process for reviewing changes ?
My process :
- Create a branch from develop for make changes
- Make some changes on the newly created branch
- Create the pull request from the branch and develop branch
- Wait reviews from others team members
- Make some changes if reviewers don't agree with me code
- Pull develop branch if newer commits are existing
- Mark my work as becoming reviewable again
If newer commits exists on the develop branch, some "merge commit" are available in my pull request and "pollute" the review (especially when a feature has been merged).
Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events