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?
Have you ever noticed that fixing specific problems might be a door opener for a bigger challenge, affecting a wider audience? This was exactly the case when we, as a service company working with mul...
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!
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