关于refs/for/
来源:互联网 发布:mysql insert into举例 编辑:程序博客网 时间:2024/06/05 16:39
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/<BRANCH>. This pushes your changes to the staging area (in the diagram, "Pending Changes"). Gerrit doesn't actually have a branch called <BRANCH>; 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/<BRANCH> 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/<BRANCH>. This way, successfully reviewed patches can be pulled directly from the correct branches of the Authoritative Repository.
- 关于refs/for/
- 关于refs/for/
- 关于refs/for/
- [Git] 关于refs/for/ 和refs/heads/
- [Git] 关于refs/for/ 和refs/heads/
- [Git] 关于refs/for/ 和refs/heads/
- [Git] 关于refs/for/ 和refs/heads/
- refs/for/ 与refs/heads/
- git中refs/for 和refs/heads
- git push . :refs/for/foo 意思
- 关于Windows 8 上的 ReFS 文件系统
- Bug for heat template: ResourceGroup中的refs属性不支持索引
- fatal One or more refs for names blocks change upload
- One or more refs/for/ names blocks change upload
- 关于RN的直接操作和ref/refs的使用
- Gerrit评审报错[remote rejected] develop-> refs/for/develop(no new changes)
- git push error report: ! [remote rejected] master -> refs/for/master (no new changes)
- SourceTree Started GET "/moshilei/test.git/info/refs?service=git-upload-pack" for...
- Android开发之解决软键盘把原来的布局给顶上去的方法
- 《TCP/IP详解 卷1:协议》 读书笔记 第23章 TCP的保活定时器
- 安装MySQL-Python出错mysql_config not found
- 安卓手机利用html5 ,video+canvas从视频流里面截图拍照
- (36)目标点Actor
- 关于refs/for/
- 使用for、if语句添加用户的一个shell脚本
- Eclipse快捷键和常用开发技巧总结
- lesson6.7Properties类
- 编辑器vim
- zabbix自定义脚本
- 属性选择器配合location使用(菜鸟的记录)
- ffmpeg实战教程(十)ffmpeg/camera实现最近很火的视频壁纸,相机壁纸
- vue 图片上传 图片展示 bootstrap