Pre-commit review from git patch separates changes into two trees

Hi

I have created a git patch file

git diff - -U999999  TARGET_BRANCH > my.patch

and uploaded it to create a pre-commit review.

This reults in a review with two trees. New/modified files are displayed under tree "a" and new files are displayed under tree "b". I guess this is related to gits use of "A" to represent the file pre-change and "b" to reflect the file post-change. This distinction has not relevance in the context of a Crucible review.

Do I need to create my patch ion a different way to prevent this from happening?

Thanks

1 answer

This widget could not be displayed.

Could you post a sample of your patch file?

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted 6 hours ago in Teamwork

What teamwork quotes inspire you?

Hey everyone! My name is Natalie and I'm an editor of the Atlassian Blog and I've got a question for you: What's your favorite quote about teamwork?  We've compiled a list here, along with...

17 views 0 4
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you