如何使用Gerrit做开发分支的备份？ [英] How to do backup of development branches with Gerrit?

问题描述

我正在使用Gerrit来管理我的git存储库。修补程序发送到Gerrit服务器并在批准时合并到git存储库中。但是，一个功能通常需要花费一些时间才能开发，开发人员希望将代码的备份保存在开发中。显而易见的解决方案是直接将分支推送到Gerrit，然后 https：/ /code.google.com/p/gerrit/issues/detail?id=1986 阻止我提交此分支进行审核。

可能的破解是当我想将它提交给审查时删除远程分支。第二个是重新设置远程分支，并在我想提交它时进行更新。

你如何处理这个问题？

解决方案

您是否尝试了参考草案？代码备份时非常有用，无需将其列为开放式补丁集。然后如果代码准备好了，它可以发布。我的建议是避免检查多个提交。更多的提交/更改难以在评论中高效。

I'm using Gerrit to manage my git repository. Patches are sent to Gerrit server and merged into the git repository when they are approved. However, often a feature takes some time to develop and the developer wants to keep a backup of the code under development. The obvious solution is to push the branch directly to Gerrit, but then https://code.google.com/p/gerrit/issues/detail?id=1986 prevents me from submitting this branch to review.

A possible hack is to remove the remote branch when I want to submit it to review. A second one is to rebase the remote branch and update change IDs when I want to submit it to review.

How do you handle this problem?

解决方案

Have you tried the draft reference? It is useful when a code should backup, without listing it as an open patchset. Then if the code is ready it can be published. My suggestion is to avoid reviewing more then one commit. More commits/changes harder to be efficient on a review.

这篇关于如何使用Gerrit做开发分支的备份？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！