关于refs/for/ 和refs/heads/

https://www.cnblogs.com/onelikeone/p/6857932.html

1. 这个不是git的规则，而是gerrit的规则，

2. Branches, remote-tracking branches, and tags等等都是对commite的引用（reference）,引用都以 “refs/……”表示. 比如remote branch: origin/git_int(=refs/remotes/origin/git_int)， local tag: v2.0(=refs/tags/v2.0)， local branch: git_int(=refs/heads/git_int)…

3. 简单点说，就是refs/for/mybranch需要经过code review之后才可以提交；refs/heads/mybranch不需要code review。

（since you want to directly push into the branch, rather than create code reviews. Pushing to refs/for/* creates code reviews which must be approved and then submitted. Pushing to refs/heads/* bypasses review entirely, and just enters the commits directly into the branch. The latter does not check committer identity, making it appropriate for importing past project history）

如果需要code review，直接push

$git push origin master

那么就会有“! [remote rejected] master -> master (prohibited by Gerrit)”的错误信息

而这样push就没有问题，

$git push origin HEAD:refs/for/mybranch

下面一段是对“refs/for”更详细的描述：

The documentation for Gerrit explains that you push to the “magical refs/for/‘branch’ ref using any Git client tool”.

This image is taken from the Intro to Gerrit. When you push to Gerrit, you do git push gerrit HEAD:refs/for/. This pushes your changes to the staging area (in the diagram, “Pending Changes”). Gerrit doesn’t actually have a branch called ; it lies to the git client.

Internally, Gerrit has it’s own implementation for the Git and SSH stacks. This allows it to provide the “magical” refs/for/ refs.

When a push request is received to create a ref in one of these namespaces Gerrit performs its own logic to update the database, and then lies to the client about the result of the operation. A successful result causes the client to believe that Gerrit has created the ref, but in reality Gerrit hasn’t created the ref at all.

After a successful patch (i.e, the patch has been pushed to Gerrit, [putting it into the “Pending Changes” staging area], reviewed, and the review has passed), Gerrit pushes the change from the “Pending Changes” into the “Authoritative Repository”, calculating which branch to push it into based on the magic it did when you pushed to refs/for/. This way, successfully reviewed patches can be pulled directly from the correct branches of the Authoritative Repository.

关于refs/for/ 和refs/heads/相关推荐

[Git] 关于refs/for/ 和refs/heads/
转载自: http://lishicongli.blog.163.com/blog/static/146825902013213439500/ 1. 这个不是git的规则,而是gerrit的规 ...
refs win10_Win10创建ReFS文件系统分区教程
你知道吗?Windows10中隐藏着一种神秘的ReFS文件系统,ReFS分区可以更可靠稳定地储存数据.但是由于ReFS文件系统的特殊性,所以想要创建ReFS分区不能像常规的Win10硬盘分区那样来实现 ...
refs win10_win10系统ReFS 3.2分区的操作方法
很多小伙伴都遇到过对 Win10创意者 1.准备一个空白的分区,这里以K盘为例: 2.按下[Win+R]打开运行,输入:regedit 点击确定打开注册表: 3.在注册表左侧依次展开:HKEY_LOC ...
refs win10_在refs格式下可不可以装windows 10
在refs格式下能装windows 10 方法一:出现上述问题后,直接把U盘拔掉插到其它电脑,把U盘里的efi文件夹和bootmgr.efi文件删掉,问题就搞定了,然后,再用这个U盘启动盘去装系统, ...
gerrit refs相关的一些小研究
gerrit 作为 code review使用不算难,然鹅,总有一些内容知其然不知其所以然,这里稍作研究和记录. 1. refs/for 和 refs/heads 向gerrit服务器提交代码命令: ...
gerrit refs相关的一些研究
gerrit 作为 code review使用不算难,然鹅,总有一些内容知其然不知其所以然,这里稍作研究和记录. 1. refs/for 和 refs/heads 向gerrit服务器提交代码命令: ...
this. $ refs: undefined 的解决办法
vue this.$refs.tree.setCheckedKeys(list) 不能用的解决办法代码 this.$refs.tree1.setCheckedKeys(list); //通过 id ...
Windows 10如何启用ReFS弹性文件系统
责任编辑:editor005 | 2016-10-10 14:26:56 本文摘自:51CTO 自微软为 Windows 操作系统定制和设计 NTFS 文件系统之后,用户的数据存储需求还是发生的巨大 ...
reactJS -- 9 组件的Refs(操作DOM的两种方法)
2019独角兽企业重金招聘Python工程师标准>>> 一.概述 https://react-cn.github.io/react/docs/more-about-refs.html ...

关于refs/for/ 和refs/heads/

关于refs/for/ 和refs/heads/相关推荐

最新文章

热门文章