blocks|key|3158468|text|我最终编写了一个新的git-submit脚本：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3158469|#!/bin/sh+-e

if+[+-z+"$1"+];+then
++++REMOTE=origin
else
++++REMOTE=$1
fi

BRANCH=`git+symbolic-ref+HEAD`
case+$BRANCH+in
++++refs/heads/*)
++++++++BRANCH=`basename+$BRANCH`
++++++++;;
++++*)
++++++++echo+"I+can't+figure+out+which+branch+you+are+on."
++++++++exit+1
++++++++;;
esac

git+push+$REMOTE+HEAD:refs/for/$BRANCH|code-block|syntax|javascript|3158470|我将此脚本放在/usr/local/libexec/git-core/git-submit中，现在有一个命令可以将新代码提交给Gerrit进行审查：|3158471|$+git+submit|3158472|如果Gerrit不是origin+remote，那么可以适当地使用git+submit+<remote>。|3158473|entityMap^0|A|A|0|0|7|12|0|0|A|6|X|J|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|Z|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|10|8|@$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|R|$]]

I ended up writing a new <code>git-submit</code> script:

<pre><code>#!/bin/sh -e

if [ -z "$1" ]; then
 REMOTE=origin
else
 REMOTE=$1
fi

BRANCH=`git symbolic-ref HEAD`
case $BRANCH in
 refs/heads/*)
 BRANCH=`basename $BRANCH`
 ;;
 *)
 echo "I can't figure out which branch you are on."
 exit 1
 ;;
esac

git push $REMOTE HEAD:refs/for/$BRANCH
</code></pre>

I put this script in <code>/usr/local/libexec/git-core/git-submit</code> and now there's one command to submit new code to Gerrit for review:

<pre><code>$ git submit
</code></pre>

If Gerrit is not the <code>origin</code> remote, then use <code>git submit &lt;remote&gt;</code> as appropriate.

blocks|key|255469|text|git+config+push.default+upstream
git+config+branch.work1234.merge+refs/for/work1234
git+config+branch.work1234.remote+origin|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|255470|或.git/config：|unstyled|255471|[push]
++++++++default+=+upstream
[branch+"work1234"]
++++++++merge+=+refs/for/work1234
++++++++remote+=+origin|255472|我不确定是否有一种方法可以将通配符放在任何地方，使其对所有分支都有效。|255473|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|N|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$B|C]]|$1|I|3|J|5|F|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|F|7|Q|8|@]|9|@]|A|$]]]|L|$]]

<pre><code>git config push.default upstream
git config branch.work1234.merge refs/for/work1234
git config branch.work1234.remote origin
</code></pre>

or .git/config:

<pre><code>[push]
 default = upstream
[branch "work1234"]
 merge = refs/for/work1234
 remote = origin
</code></pre>

I'm not sure if there's a way to put a wildcard in there anywhere to make it work for all branches.

blocks|key|260631|text|我找到了两个选择：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|260632|1)看看我做的一个项目，ggh：https://github.com/hobbs/ggh|offset|length|260633|2)您可以在遥控器中配置默认的推流refspec。我只知道如何使用硬编码的远程分支来做到这一点，仍然在尝试如何通配远程refspec，以便它始终推送到您正在跟踪的远程分支：|260634|[remote+"origin"]
++++fetch+=+%2Brefs/heads/*:refs/remotes/origin/*
++++url+=+ssh://gerrit/repo
++++push+=++HEAD:refs/for/master|code-block|syntax|javascript|260635|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/hobbs/ggh^0|0|G|S|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@$D|W|E|X|1|Y]]|A|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|10|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

Two options I've found:

1) Check out a project I made, ggh: <a href="https://github.com/hobbs/ggh" rel="nofollow">https://github.com/hobbs/ggh</a>

2) You can configure the default push refspec in your remote. I've only figured out how to do this with a hardcoded remote branch, still trying to figure out how to wildcard the remote refspec so that it always pushes to the remote you're tracking:

<pre><code>[remote "origin"]
 fetch = +refs/heads/*:refs/remotes/origin/*
 url = ssh://gerrit/repo
 push = HEAD:refs/for/master
</code></pre>

blocks|key|257596|text|这是Greg+Hewgill答案的改进。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|257597|在路径上的某个地方创建一个脚本，比如在您的profile+bin文件夹中(如果需要，甚至在Windows上也可以创建一个)：|257598|$+mkdir+~/bin
$+vi+~/bin/git-submit|code-block|syntax|javascript|257599|内容如下：|257600|#!/bin/sh+-e

if+[+-z+"$1"+];+then
++++REMOTE=origin
else
++++REMOTE=$1
fi

BRANCH=`git+symbolic-ref+HEAD`
case+$BRANCH+in
++++refs/heads/*)
++++++++BRANCH=`basename+$BRANCH`
++++++++;;
++++*)
++++++++echo+"I+can't+figure+out+which+branch+you+are+on."
++++++++exit+1
++++++++;;
esac

REMOTE_BRANCH=`git+config+--get+"branch.$BRANCH.merge"`
if+[+-z+$REMOTE_BRANCH+]
then
++++echo+"There+is+no+tracking+information+for+the+current+branch."
++++echo+"If+you+wish+to+set+tracking+information+for+this+branch+you+can+do+so+with:"
++++echo+""
++++echo+"++++git+branch+--set-upstream+$BRANCH+<remote>/<branch>"
++++echo+""
++++exit+1
fi

git+push+$REMOTE+HEAD:refs/for/$REMOTE_BRANCH|257601|假设您创建了一个远程跟踪分支，如下所示：|257602|$+git+checkout+-b+MyBranch+origin/master|257603|您可以简单地调用：|257604|$+git+submit|257605|..。在这种情况下推送到refs/for/master。|offset|length|style|CODE|257606|entityMap^0|0|0|0|0|0|0|0|0|0|C|F|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|14|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|15|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|16|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|17|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|18|8|@]|9|@]|A|$G|H]]|$1|Q|3|R|5|6|7|19|8|@]|9|@]|A|$]]|$1|S|3|T|5|F|7|1A|8|@]|9|@]|A|$G|H]]|$1|U|3|V|5|6|7|1B|8|@$W|1C|X|1D|Y|Z]]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|11|$]]

Here is an improvement of Greg Hewgill answer.

Create a script somewhere on the path, like on your profile bin folder (create one if necessary, even on Windows):

<pre><code>$ mkdir ~/bin
$ vi ~/bin/git-submit
</code></pre>

With the following content:

<pre><code>#!/bin/sh -e

if [ -z "$1" ]; then
 REMOTE=origin
else
 REMOTE=$1
fi

BRANCH=`git symbolic-ref HEAD`
case $BRANCH in
 refs/heads/*)
 BRANCH=`basename $BRANCH`
 ;;
 *)
 echo "I can't figure out which branch you are on."
 exit 1
 ;;
esac

REMOTE_BRANCH=`git config --get "branch.$BRANCH.merge"`
if [ -z $REMOTE_BRANCH ]
then
 echo "There is no tracking information for the current branch."
 echo "If you wish to set tracking information for this branch you can do so with:"
 echo ""
 echo " git branch --set-upstream $BRANCH &lt;remote&gt;/&lt;branch&gt;"
 echo ""
 exit 1
fi

git push $REMOTE HEAD:refs/for/$REMOTE_BRANCH
</code></pre>

Supposing you create a remote tracking branch like:

<pre><code>$ git checkout -b MyBranch origin/master
</code></pre>

You can simply call:

<pre><code>$ git submit
</code></pre>

... to push to <code>refs/for/master</code> in this case.

I'm setting up Git with <a href="https://code.google.com/p/gerrit/" rel="noreferrer">Gerrit Code Review</a> and am looking for a way to make the necessary Git commands relatively straightforward for users who might be new to Git.

The commands I currently have for starting a new feature branch are essentially (assuming Gerrit is <code>origin</code>):

<pre><code>git checkout baseline
git pull
git checkout -b work1234
git push -u origin work1234
</code></pre>

This starts a new work package <code>work1234</code> branched from some <code>baseline</code>, and the final push creates the branch in Gerrit and sets the upstream. So <code>.git/config</code> looks something like:

<pre><code>[branch "work1234"]
 remote = origin
 merge = refs/heads/work1234
</code></pre>

Now, Gerrit wants new commits for review to be pushed to a special refspec, <code>refs/for/work1234</code> for example. I can do this manually with:

<pre><code>git push origin work1234:refs/for/work1234
</code></pre>

What I would like to do is find some way to set up <code>.git/config</code> so that a plain <code>git push</code> will push the current branch to the refspec on the remote that Gerrit requires. I have looked at the following <code>git config</code> areas:

<ul>
<li><code>branch.&lt;name&gt;.*</code> - doesn't seem to have any specific option for setting the push refspec</li>
<li><code>push.default</code> - I sort of want <code>upstream</code> here</li>
<li><code>remote.&lt;name&gt;.push</code> - I tried <code>refs/heads/*:refs/for/*</code> here but <code>git push</code> always wants to push all local branches in this case, while I just want the current branch</li>
</ul>

If I can't make Git do this by itself, I'll write a small wrapper script that fully specifies the refspecs. However, it would be better if Git could push to the right place natively.

How to configure specific upstream push refspec for Git when used with Gerrit?

Windows

我正在用设置Git，并且正在寻找一种方法，使必要的Git命令对于可能是Git新手的用户来说相对简单。我目前用来启动一个新特性分支的命令基本上是(假设Gerrit是origin)：git checkout baselinegit pullgit checkout -b work1234git push -u origin...

问在使用Gerrit时，如何为Git配置特定的上游推送refspec？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在使用Gerrit时，如何为Git配置特定的上游推送refspec？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在使用Gerrit时，如何为Git配置特定的上游推送refspec？
EN