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

Could you post a sample of your patch file?

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 08, 2018 in Teamwork

If you could delete any meeting from your calendar, which one would it be?

Let’s face it: most of us have too many meetings on our calendars. And few things are a bigger waste of time than recurring meetings that no longer provide any value to attendees (or the busines...

347 views 11 9
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