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

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
Published in Agile

Webinar: Dean Leffingwell and Steve Elliot present on SAFe 5.0, come ask Dean and Steve questions!

...steemed Steve Elliot (head of product for Jira Align). Agenda: What’s new or changed in SAFe 5.0: Introduction of OKRs Essential SAFe How to achieve true business a...

120 views 0 1
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