As per your lastest response, I believe you are expecting you can perform the commit within FishEye, is this correct?
If so, I'd like to inform that you actually need to just perform the commit in your repository - the pre-commit review is meant to allow you to create a patch and review it before it is committed. Once it is reviewed, you have to perform the commit directly in the repository, as FishEye doesn't write any information in your repository, it only reads from it.
Ok. Is there a way to enfornce than that the commited svn patch is exactly same as patch reviewed in pre-commit review in fish eye?
The idea is basically same, regardless who is commiting to svn, tighly sync what's reviewed and what's commited to svn.
Thanks for your help!
The pre-commit patch you upload to perform the review is made of a diff showing the difference between the version that is already in the repository and the version that is about to be committed. I suppose the person who created the patch submitted it to review, and is just waiting for approval to perform the commit, so after the review is closed and the change is approved I think it would be just a matter of having this person performing the commit.
If the person made new changes while the pre-committed change is still being reviewed I think the process would consist of having this person generating a new patch to be reviewed, so the latest changes would be reviewed before being committed.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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