We suggest developers to logically split a big change into multiple smaller patches, so we can review them more easily. For example, I want to add a feature, this feature involves refactor existing codes. So for easily review, I want to split this big change into 2 parts:
1. Refactor existing codes, which doesn't introduce any functional changes.
2. Add new codes that implementing feature.
These 2 patches formed as a patch series, we have to review patch 2 after patch 1 is reviewed. In other words, These 2 patches (or reviews) has dependence. So how to create reviews of these 2 patches?
I have seen someone ask a same question in https://community.atlassian.com/t5/Fisheye-Crucible-questions/Crucible-how-to-review-a-series-of-patch/qaq-p/841110, but it does resolved. Could someone help me?
Hello Community! Quick disclaimer: We are running a contest on Community (The Atlympics!) from July 23rd - August 8th of 2021. If you are interested in participating in this contest (prizes! ...
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