blocks|key|1950508|text|预收钩子，如：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1950509|#!/bin/sh

while+read+from+to+ref;+do
++++git+log+--format=%25B+-n+1+"$to"+\
++++++++%7C+if+grep+-q+pattern;+then+exit+1;+fi
done|code-block|syntax|javascript|1950510|将拒绝主题与模式匹配的任何提交。你几乎可以肯定地让它做你想做的事情(例如，使用grep+"Merge+remote-tracking+branch")。详情请参见githooks(5)。|offset|length|style|CODE|1950511|entityMap^0|0|0|13|Z|29|B|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]|$I|T|J|U|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

A pre-receive hook like:

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

while read from to ref; do
 git log --format=%B -n 1 "$to" \
 | if grep -q pattern; then exit 1; fi
done
</code></pre>

will reject any commit in which the subject matches the pattern. You can almost certainly make this do what you want (eg, use <code>grep "Merge remote-tracking branch"</code>). See <code>githooks(5)</code> for details.

blocks|key|1950583|text|考虑到GitHub操作还不支持预接收钩子类型的操作(如这里提到的+)，您需要：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1950584|要么是GitHub企业中的预接收钩子+(参见"在GitHub企业中使用预接收钩子")|unordered-list-item|1950585|或在基础设施上设置侦听器，以侦听GitHub(.com)+WebHook|1950586|注:9月2020年:+GitHub的行动开始成为可用于GitHub企业的beta版。|1950587|注意，通过启用2019年12月4日，您可以通过拒绝包含合并提交的任何推送来保护分支。|1950588|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/57742838/6309|1|https://help.github.com/en/enterprise/2.17/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance|2|https://github.community/t5/GitHub-Enterprise-Best-Practices/Using-pre-receive-hooks-in-GitHub-Enterprise/ba-p/13863|3|https://github.com/github/roadmap/issues/100|4|https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/^0|R|5|0|0|3|F|1|N|H|2|0|0|O|H|3|0|7|A|4|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@$A|13|B|14|1|15]]|C|$]]|$1|D|3|E|5|F|7|16|8|@]|9|@$A|17|B|18|1|19]|$A|1A|B|1B|1|1C]]|C|$]]|$1|G|3|H|5|F|7|1D|8|@]|9|@]|C|$]]|$1|I|3|J|5|6|7|1E|8|@]|9|@$A|1F|B|1G|1|1H]]|C|$]]|$1|K|3|L|5|6|7|1I|8|@]|9|@$A|1J|B|1K|1|1L]]|C|$]]|$1|M|3|-4|5|6|7|1M|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]|U|$5|P|Q|R|C|$S|V]]|W|$5|P|Q|R|C|$S|X]]|Y|$5|P|Q|R|C|$S|Z]]|10|$5|P|Q|R|C|$S|11]]]]

Considering GitHub actions do not support yet a pre-receive hook type of action, as <a href="https://stackoverflow.com/a/57742838/6309">mentioned here</a>, you would need:
<ul>
<li>either a <a href="https://help.github.com/en/enterprise/2.17/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance" rel="nofollow noreferrer">pre-receive hook in your GitHub Enterprise</a> (see &quot;<a href="https://github.community/t5/GitHub-Enterprise-Best-Practices/Using-pre-receive-hooks-in-GitHub-Enterprise/ba-p/13863" rel="nofollow noreferrer">Using pre-receive hooks in GitHub Enterprise</a>&quot;)</li>
<li>or setting up a listener on your infrastructure, to listen to a GitHub(.com) WebHook</li>
</ul>
Note: Sept. 2020: GitHub Actions are starting to be <a href="https://github.com/github/roadmap/issues/100" rel="nofollow noreferrer">available for GHE (GitHub Enterprise) in beta</a>.
<hr />
Note that <a href="https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/" rel="nofollow noreferrer">Dec. 4th 2019</a>, you can protect a branch by rejecting any push that contains a merge commit by enabling <code>Require linear history</code>.
<hr />

blocks|key|1739982|text|正如其他人所提到的，您可以在pre-receive企业中使用GitHub挂钩，但不能使用GitHub.com。这是因为pre-receive钩子是任意代码，GitHub在它们的服务器上运行任意代码是没有意义的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1739983|您可以使用分支保护，并要求拉请求合并到某些分支，然后使用GitHub操作(或其他CI工具)拒绝包含合并的分支。这是大多数团队处理拒绝不符合某些标准的提交的典型方法。|1739984|entityMap^0|E|B|1N|B|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

As others have mentioned, you can use a <code>pre-receive</code> hook in GitHub Enterprise, but not GitHub.com. That's because <code>pre-receive</code> hooks are arbitrary code, and it doesn't make sense for GitHub to run your arbitrary code on their servers.

It is possible for you to use branch protection and require pull requests to merge into certain branches, and then use GitHub Actions (or some other CI tool) to reject branches containing merges. That's the typical approach that most teams take to handle rejecting commits that don't meet some set of criteria.

In our project, we usually use a rebase-and-push workflow. Large features on different branches are merged through GitHub's UI, which show up as "Merge pull request".

Sometimes one of us does something wrong and ends up with a commit that looks like "Merge remote-tracking branch 'origin/master'". Is there any way that we can auto-deny a push to master if the push contains commits with "Merge remote-tracking branch" in the title?

On GitHub, is it possible to deny a push based on the title of the commits?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在我们的项目中，我们通常使用重基和推送工作流。不同分支上的大型特性通过GitHub的UI合并，显示为“合并拉请求”。有时，我们中的一个人做错了什么，最后提交了一个看起来像“合并远程跟踪分支‘起源/主人’”的提交。如果推送包含标题中包含有“合并远程跟踪分支”的提交，我们是否可以自动拒绝该推送？

问在GitHub上，可以根据提交的标题拒绝推送吗？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在GitHub上，可以根据提交的标题拒绝推送吗？EN