上传补丁集并保留现有评论 [英] Upload patch set preserving existing reviews

查看:150
本文介绍了上传补丁集并保留现有评论的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们使用Jenkins验证补丁集.有时,詹金斯需要对补丁集进行一些更改.因此,它commit --amend进行了更改,然后上传了新的补丁集.

We use Jenkins to verify patch sets. Sometimes Jenkins needs do some changes on the patch set. So it commit --amend the changes and then uploads the new patch set.

除了可以删除对原始补丁集所做的所有手动检查之外,它还可以很好地发挥作用.

It work nicely besides the fact, that all manual reviews made to the original patch set get erased.

  • 如何在不失去所有现有评论/投票的情况下推送新的补丁集(来自Jenkins)?

推荐答案

请注意,在您描述的情况下,您拥有一个新的补丁集,并且在特殊情况下(不包括特殊情况),您不希望获得该补丁集的票复制到新的补丁集.例如:如果有人批准了patchset1,而Jenkins推送了patchset2,则可能他/她不想将他/她的投票自动复制到patchset2.

Be aware that, in the situation you have described, you have a new patchset and, excluding in special situations, you don't want votes of the old patchset copied forward to the new patchset. For example: if someone have approved the patchset1 and Jenkins pushes the patchset2, probably he/she doesn't want to have his/her vote automatically copied to patchset2.

表示:您可以控制将/不将投票复制到新的补丁集的方式,设置项目的label.LABEL-NAME.copyXXXXX选项.请参阅此处.

Said that: you can control how votes will/won't be copied forward to new patchset setting the label.LABEL-NAME.copyXXXXX options of the project. See more info in Gerrit documentation here.

这篇关于上传补丁集并保留现有评论的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆