blocks|key|571552|text|post-receive钩子在stdin上获取的最后一个参数是ref被更改的内容，因此我们可以使用该参数来检查该值是否为“refs/head/master”。一个类似于我在post-receive钩子中使用的ruby：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|571553|STDIN.each+do+%7Cline%7C
++++(old_rev,+new_rev,+ref_name)+=+line.split
++++if+ref_name+=~+/master/
+++++++++#+do+your+push
++++end
end|code-block|syntax|javascript|571554|请注意，它会为每个被推送的ref获取一行，所以如果您推送的不只是master，它仍然可以工作。|571555|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

The last parameter that a post-receive hook gets on stdin is what ref was changed, so we can use that to check if that value was "refs/heads/master." A bit of ruby similar to what I use in a post-receive hook:

<pre><code>STDIN.each do |line|
 (old_rev, new_rev, ref_name) = line.split
 if ref_name =~ /master/
 # do your push
 end
end
</code></pre>

Note that it gets a line for each ref that was pushed, so if you pushed more than just master, it will still work.

blocks|key|571592|text|Stefan的回答对我不起作用，但this做到了：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|571593|#!/bin/bash

echo+"determining+branch"

if+!+[+-t+0+];+then
++read+-a+ref
fi

IFS='/'+read+-ra+REF+<<<+"${ref[2]}"
branch="${REF[2]}"

if+[+"master"+==+"$branch"+];+then
++echo+'master+was+pushed'
fi

if+[+"staging"+==+"$branch"+];+then
++echo+'staging+was+pushed'
fi

echo+"done"|code-block|syntax|javascript|571594|entityMap|0|LINK|mutability|MUTABLE|url|https://gist.github.com/3697539^0|H|4|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

Stefan's answer didn't work for me, but <a href="https://gist.github.com/3697539" rel="noreferrer">this</a> did:

<pre><code>#!/bin/bash

echo "determining branch"

if ! [ -t 0 ]; then
 read -a ref
fi

IFS='/' read -ra REF &lt;&lt;&lt; "${ref[2]}"
branch="${REF[2]}"

if [ "master" == "$branch" ]; then
 echo 'master was pushed'
fi

if [ "staging" == "$branch" ]; then
 echo 'staging was pushed'
fi

echo "done"
</code></pre>

blocks|key|787677|text|post-receive钩子从stdin获取其参数，格式为：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|787678|<oldrev>+<newrev>+<refname>|code-block|syntax|javascript|787679|由于这些参数来自标准输入，而不是来自命令行参数，因此需要使用read而不是$1+$2+$3。|offset|length|style|CODE|787680|post-receive钩子可以一次接收多个分支(例如，如果有人执行git+push+--all)，因此我们还需要将read包装在while循环中。|787681|正常工作的代码片段如下所示：|787682|#!/bin/bash
while+read+oldrev+newrev+refname
do
++++branch=$(git+rev-parse+--symbolic+--abbrev-ref+$refname)
++++if+[+"master"+=+"$branch"+];+then
++++++++#+Do+something
++++fi
done|787683|entityMap^0|0|0|U|4|11|8|0|Y|E|1M|4|1T|5|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@$I|X|J|Y|K|L]|$I|Z|J|10|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|11|8|@$I|12|J|13|K|L]|$I|14|J|15|K|L]|$I|16|J|17|K|L]]|9|@]|A|$]]|$1|O|3|P|5|6|7|18|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|19|8|@]|9|@]|A|$E|F]]|$1|S|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|T|$]]

A post-receive hook gets its arguments from stdin, in the form:
<pre><code>&lt;oldrev&gt; &lt;newrev&gt; &lt;refname&gt;
</code></pre>
Since these arguments are coming from stdin, not from a command line argument, you need to use <code>read</code> instead of <code>$1 $2 $3</code>.
The post-receive hook can receive multiple branches at once (for example if someone does a <code>git push --all</code>), so we also need to wrap the <code>read</code> in a <code>while</code> loop.
A working snippet looks something like this:
<pre class="lang-bash prettyprint-override"><code>#!/bin/bash
while read oldrev newrev refname
do
 branch=$(git rev-parse --symbolic --abbrev-ref $refname)
 if [ &quot;master&quot; = &quot;$branch&quot; ]; then
 # Do something
 fi
done
</code></pre>

blocks|key|787719|text|上面的解决方案对我都不起作用。经过大量的调试之后，事实证明使用'read‘命令是行不通的--相反，用通常的方式解析命令行参数就行得通。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|787720|这就是我刚刚在CentOS+6.3上成功测试的更新后钩子。|787721|#!/bin/bash

echo+"determining+branch"

branch=`echo+$1+%7C+cut+-d/+-f3`

if+[+"master"+==+"$branch"+];+then
++++echo+"master+branch+selected"
fi

if+[+"staging"+==+"$branch"+];+then
++++echo+"staging+branch+selected"
fi

exec+git+update-server-info|code-block|syntax|javascript|787722|更新:更奇怪的是，预接收钩子通过stdin接受其输入，因此使用'+read‘读取(哇，从没想过我会这么说)。对我来说，更新后的钩子仍然只需1美元。|787723|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Neither of the solutions above worked for me. After much, much debugging, it turns out that using the 'read' command doesn't work -- instead, parsing command line arguments the usual way works fine.

Here is the exact post-update hook that I just successfully tested now on CentOS 6.3.

<pre><code>#!/bin/bash

echo "determining branch"

branch=`echo $1 | cut -d/ -f3`

if [ "master" == "$branch" ]; then
 echo "master branch selected"
fi

if [ "staging" == "$branch" ]; then
 echo "staging branch selected"
fi

exec git update-server-info
</code></pre>

UPDATE: on an even stranger note, the pre-receive hook takes its input via stdin, therefore read with 'read' (wow, never thought I'd say that). The post-update hook still works with $1 for me.

blocks|key|571692|text|我已经为自己编写了一个PHP脚本来实现此功能。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|571693|https://github.com/fotuzlab/githubdump-php|offset|length|571694|在你的服务器上托管这个文件，最好是repo+root，并在github+webhooks中定义url。将第8行的'allcommits‘更改为您的分支名称，并在第18行添加您的代码/函数。|571695|例如：|571696|function+githubdump($payload_object)+{
++++//+Write+your+code+here.
++++exec('git+push+origin+master');
}|code-block|syntax|javascript|571697|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|16|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|F|3|G|5|6|7|10|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|11|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|12|8|@]|9|@]|A|$M|N]]|$1|O|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|C]]]]

I had written a PHP script for myself to do this functionality.

<a href="https://github.com/fotuzlab/githubdump-php" rel="nofollow">https://github.com/fotuzlab/githubdump-php</a>

Host this file on your server, preferably repo root and define the url in github webhooks. Change 'allcommits' on line 8 with your branch name and add your code/function at line 18.

e.g.

<pre><code>function githubdump($payload_object) {
 // Write your code here.
 exec('git push origin master');
}
</code></pre>

blocks|key|571729|text|简单的方法，在git+hook中编写|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|571730|read+refname
echo+$refname|code-block|syntax|javascript|571731|简单-关于这个伟大的链接hooking+system的更多信息|571732|entityMap|0|LINK|mutability|MUTABLE|url|http://demonastery.org/2012/09/a-hooking-system-for-gitolite/^0|7|8|0|0|C|E|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Y|8|@]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|M|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

Simple approach, in <code>git hook</code> write

<pre><code>read refname
echo $refname
</code></pre>

Simple - more info on this great link <a href="http://demonastery.org/2012/09/a-hooking-system-for-gitolite/" rel="nofollow">hooking system</a>

blocks|key|571761|text|来自@pauljz的答案对于某些git钩子来说工作得很好，比如pre-push，但是pre-commit不能访问这些变量oldrev+newrev+refname|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|571762|所以我创建了这个备用版本，它适用于pre-commit，或者实际上是和钩子。这是一个pre-commit钩子，如果我们不在master分支上，它将运行一个husky脚本。|571763|#!/bin/bash
#+git+'commit'+does+not+have+access+to+these+variables:+oldrev+newrev+refname
#+So+get+the+branch+name+off+the+head

branchPath=$(git+symbolic-ref+-q+HEAD)+#+Something+like+refs/heads/myBranchName
branch=${branchPath##*/}++++++#+Get+text+behind+the+last+/+of+the+branch+path

echo+"Head:+$branchPath";
echo+"Current+Branch:+$branch";

if+[+"master"+!=+"$branch"+];+then

+++#+If+we're+NOT+on+the+Master+branch,+then+Do+something
+++#+Original+Pre-push+script+from+husky+0.14.3

+++command_exists+()+{
+++++command+-v+"$1"+>/dev/null+2>&1
+++}

+++has_hook_script+()+{
+++++[+-f+package.json+]+&&+cat+package.json+%7C+grep+-q+"\"$1\"[[:space:]]*:"
+++}

+++cd+"frontend"+#+change+to+your+project+directory,+if+.git+is+a+level+higher

+++#+Check+if+precommit+script+is+defined,+skip+if+not
+++has_hook_script+precommit+%7C%7C+exit+0

+++#+Node+standard+installation
+++export+PATH="$PATH:/c/Program+Files/nodejs"

+++#+Check+that+npm+exists
+++command_exists+npm+%7C%7C+{
+++++echo+>&2+"husky+>+can't+find+npm+in+PATH,+skipping+precommit+script+in+package.json"
+++++exit+0
+++}

+++#+Export+Git+hook+params
+++export+GIT_PARAMS="$*"

+++#+Run+npm+script
+++echo+"husky+>+npm+run+-s+precommit+(node+`node+-v`)"
+++echo

+++npm+run+-s+precommit+%7C%7C+{
+++++echo
+++++echo+"husky+>+pre-commit+hook+failed+(add+--no-verify+to+bypass)"
+++++exit+1
+++}
fi|code-block|syntax|javascript|571764|我希望这对某些人有帮助。您可以根据需要轻松地修改if和fi语句之间的任何内容。|571765|entityMap^0|V|8|16|A|1O|L|0|16|A|1P|6|25|5|0|0|O|2|R|2|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@$9|Y|A|Z|B|C]|$9|10|A|11|B|C]|$9|12|A|13|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|14|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|15|8|@$9|16|A|17|B|C]|$9|18|A|19|B|C]]|D|@]|E|$]]|$1|O|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|P|$]]

The answer from @pauljz works fine for certain git hooks like <code>pre-push</code>, but <code>pre-commit</code> does not have access to those variables <code>oldrev newrev refname</code>

So I created this alternate version which works for pre-commit, or really and hook. This is a <code>pre-commit</code> hook that will run a <code>husky</code> script if we're NOT on the <code>master</code> branch.

<pre><code>#!/bin/bash
# git 'commit' does not have access to these variables: oldrev newrev refname
# So get the branch name off the head

branchPath=$(git symbolic-ref -q HEAD) # Something like refs/heads/myBranchName
branch=${branchPath##*/} # Get text behind the last / of the branch path

echo "Head: $branchPath";
echo "Current Branch: $branch";

if [ "master" != "$branch" ]; then

 # If we're NOT on the Master branch, then Do something
 # Original Pre-push script from husky 0.14.3

 command_exists () {
 command -v "$1" &gt;/dev/null 2&gt;&amp;1
 }

 has_hook_script () {
 [ -f package.json ] &amp;&amp; cat package.json | grep -q "\"$1\"[[:space:]]*:"
 }

 cd "frontend" # change to your project directory, if .git is a level higher

 # Check if precommit script is defined, skip if not
 has_hook_script precommit || exit 0

 # Node standard installation
 export PATH="$PATH:/c/Program Files/nodejs"

 # Check that npm exists
 command_exists npm || {
 echo &gt;&amp;2 "husky &gt; can't find npm in PATH, skipping precommit script in package.json"
 exit 0
 }

 # Export Git hook params
 export GIT_PARAMS="$*"

 # Run npm script
 echo "husky &gt; npm run -s precommit (node `node -v`)"
 echo

 npm run -s precommit || {
 echo
 echo "husky &gt; pre-commit hook failed (add --no-verify to bypass)"
 exit 1
 }
fi
</code></pre>

I hope that helps someone. You can easily modify for your needs, anything in between the <code>if</code> and <code>fi</code> statements.

Here's my current hook in a bare repo that lives in the company's server:
<code>git push origin master</code>
This hooks pushes to Assembla.
What i need is to push only one branch (master, ideally) when someone pushes changes to that branch on our server, and ignore pushes to other branches. Is it possible to select the branch from a bare repo and push only that branch to Assembla?

Writing a git post-receive hook to deal with a specific branch

这是我当前的钩子，位于公司的服务器上的一个简单的代码库中：git push origin master，这个钩子推送到汇编。我需要的是，当有人在我们的服务器上推送对该分支的更改时，只推送一个分支(理想情况下，主分支)，并忽略对其他分支的推送。是否可以从裸存储库中选择分支并仅将该分支推送到Assembla？

问编写一个git post-receive挂钩来处理特定的分支
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问编写一个git post-receive挂钩来处理特定的分支EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问编写一个git post-receive挂钩来处理特定的分支
EN