blocks|key|1106948|text|如果您有自己的Bitbucket服务器，您可以添加一个像"又一次提交检查器“这样的插件，它正是这样做的：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1106949|还有一个提交检查器是一个存储插件，它允许您根据可配置的规则拒绝提交到存储库。它的主要功能是要求提交消息包含有效的JIRA问题，|blockquote|1106950|看它的GitHub回购。|1106951|如果不是，作为在此讨论，您需要一个预提交钩子(客户端)或一个预接收钩子(但是对于公共BitBucket服务器，这意味着网钩)参见"钩在藏物上“。|1106952|这里中提到的“提交消息中的需求问题键”是为2017年5月BiBucket云引入的。|1106953|这个帖子补充道：|1106954|只要在存储库设置下设置链接以与JIRA挂钩，就不必在Bitbucket+Repository+->+Settings+->+Links下打开“提交消息中的要求问题密钥”。
这基本上是你设定的一条规则，任何人都不能在没有问题键的情况下推动任何事情。如果您想暂时禁用它，那么您可以随时关闭它。|style|CODE|1106955|As+这里提到的|1106956|Bitbucket服务器没有相同的选项来要求提交注释中的问题键。
为了获得该功能，您必须获得应用程序(如用于Bitbucket的Jira挂钩或更好的Bitbucket提交策略)或编写自己的应用程序。
或者：|BOLD|1106957|另一个提交检查器(a.k.a.+)(+"YACC")|unordered-list-item|1106958|控制Freak|1106959|entityMap|0|LINK|mutability|MUTABLE|url|https://marketplace.atlassian.com/plugins/com.isroot.stash.plugin.yacc/server/overview|1|https://github.com/sford/yet-another-commit-checker|2|https://answers.atlassian.com/questions/148310/how-can-i-implement-a-policy-in-stash-to-prevent-check-in-without-an-issue-linked-in-the-commit|3|https://confluence.atlassian.com/bitbucket/manage-webhooks-735643732.html|4|http://blogs.atlassian.com/2013/03/stash-git-hooks-api/|5|https://stackoverflow.com/a/60451500/6309|6|https://bitbucket.org/blog/document-changes-required-issue-keys-bitbucket-cloud|7|https://community.atlassian.com/t5/Bitbucket-questions/quot-Require-issue-keys-in-commit-messages-quot-what-about-if/qaq-p/737358|8|https://community.atlassian.com/t5/Bitbucket-questions/Require-issue-keys-in-commit-messages/qaq-p/1171253|9|https://marketplace.atlassian.com/apps/1211959/jira-hooks-for-bitbucket?hosting=server&tab=overview|10|https://marketplace.atlassian.com/apps/1214430/better-commit-policy-for-bitbucket?hosting=server&tab=overview|11|https://marketplace.atlassian.com/apps/1211854/yet-another-commit-checker?hosting=server&tab=overview|12|https://marketplace.atlassian.com/apps/1217635/control-freak-for-bitbucket-server?hosting=server&tab=overview^0|T|8|0|0|0|3|8|1|0|7|4|2|1N|2|3|1T|5|4|0|0|2|5|L|G|6|0|0|4|7|0|Q|15|0|3|5|8|0|0|J|1G|I|9|1Z|G|A|0|0|Q|B|0|0|7|C|0^^$0|@$1|2|3|4|5|6|7|1Y|8|@]|9|@$A|1Z|B|20|1|21]]|C|$]]|$1|D|3|E|5|F|7|22|8|@]|9|@]|C|$]]|$1|G|3|H|5|6|7|23|8|@]|9|@$A|24|B|25|1|26]]|C|$]]|$1|I|3|J|5|6|7|27|8|@]|9|@$A|28|B|29|1|2A]|$A|2B|B|2C|1|2D]|$A|2E|B|2F|1|2G]]|C|$]]|$1|K|3|L|5|6|7|2H|8|@]|9|@$A|2I|B|2J|1|2K]|$A|2L|B|2M|1|2N]]|C|$]]|$1|M|3|N|5|6|7|2O|8|@]|9|@$A|2P|B|2Q|1|2R]]|C|$]]|$1|O|3|P|5|F|7|2S|8|@$A|2T|B|2U|Q|R]]|9|@]|C|$]]|$1|S|3|T|5|6|7|2V|8|@]|9|@$A|2W|B|2X|1|2Y]]|C|$]]|$1|U|3|V|5|F|7|2Z|8|@$A|30|B|31|Q|W]]|9|@$A|32|B|33|1|34]|$A|35|B|36|1|37]]|C|$]]|$1|X|3|Y|5|Z|7|38|8|@]|9|@$A|39|B|3A|1|3B]]|C|$]]|$1|10|3|11|5|Z|7|3C|8|@]|9|@$A|3D|B|3E|1|3F]]|C|$]]|$1|12|3|-4|5|6|7|3G|8|@]|9|@]|C|$]]]|13|$14|$5|15|16|17|C|$18|19]]|1A|$5|15|16|17|C|$18|1B]]|1C|$5|15|16|17|C|$18|1D]]|1E|$5|15|16|17|C|$18|1F]]|1G|$5|15|16|17|C|$18|1H]]|1I|$5|15|16|17|C|$18|1J]]|1K|$5|15|16|17|C|$18|1L]]|1M|$5|15|16|17|C|$18|1N]]|1O|$5|15|16|17|C|$18|1P]]|1Q|$5|15|16|17|C|$18|1R]]|1S|$5|15|16|17|C|$18|1T]]|1U|$5|15|16|17|C|$18|1V]]|1W|$5|15|16|17|C|$18|1X]]]]

If you have your own Bitbucket server, you can add a plugin like "<a href="https://marketplace.atlassian.com/plugins/com.isroot.stash.plugin.yacc/server/overview" rel="nofollow noreferrer">Yet Another Commit Checker</a>" which does precisely that:

<blockquote>
 Yet Another Commit Checker is a Stash plugin that allows you to reject commits to a repository based on configurable rules. Its main feature is requiring commit messages to contain a valid JIRA issue, 
</blockquote>

See its <a href="https://github.com/sford/yet-another-commit-checker" rel="nofollow noreferrer">GitHub repo</a>.

If not, as <a href="https://answers.atlassian.com/questions/148310/how-can-i-implement-a-policy-in-stash-to-prevent-check-in-without-an-issue-linked-in-the-commit" rel="nofollow noreferrer">discussed here</a>, you need a pre-commit hook (client side) or a pre-receive hook (but for a public BitBucket server, that would mean a <a href="https://confluence.atlassian.com/bitbucket/manage-webhooks-735643732.html" rel="nofollow noreferrer">webhook</a>) See "<a href="http://blogs.atlassian.com/2013/03/stash-git-hooks-api/" rel="nofollow noreferrer">Hooked on Stash</a>".

<hr>

The "Require issue keys in commit messages" mentioned <a href="https://stackoverflow.com/a/60451500/6309">here</a> has been introduced for <a href="https://bitbucket.org/blog/document-changes-required-issue-keys-bitbucket-cloud" rel="nofollow noreferrer">BiBucket Cloud in May 2017</a>

<a href="https://community.atlassian.com/t5/Bitbucket-questions/quot-Require-issue-keys-in-commit-messages-quot-what-about-if/qaq-p/737358" rel="nofollow noreferrer">This thread</a> adds:

<blockquote>
 As long as you setup your links under repository settings to hook with JIRA, you do NOT HAVE TO switch on "Require issue keys in commit messages" under <code>Bitbucket Repository -&gt; Settings -&gt; Links</code>. 
 That is basically a rule you are setting that no one can push anything without issue keys. If you want to disable temporarily, then you can switch it off and on any time. 
</blockquote>

As <a href="https://community.atlassian.com/t5/Bitbucket-questions/Require-issue-keys-in-commit-messages/qaq-p/1171253" rel="nofollow noreferrer">mentioned here</a>:

<blockquote>
 Bitbucket Server does not have the same option to require issue keys in commit comments out-of-the-box. 
 You would have to get an app (like <a href="https://marketplace.atlassian.com/apps/1211959/jira-hooks-for-bitbucket?hosting=server&amp;tab=overview" rel="nofollow noreferrer">Jira hooks for Bitbucket</a> or <a href="https://marketplace.atlassian.com/apps/1214430/better-commit-policy-for-bitbucket?hosting=server&amp;tab=overview" rel="nofollow noreferrer">Better commit policy for Bitbucket</a>) or write your own in order to get that functionality. 
 Or: 
 
 <ul>
 <li><a href="https://marketplace.atlassian.com/apps/1211854/yet-another-commit-checker?hosting=server&amp;tab=overview" rel="nofollow noreferrer">Yet Another Commit Checker (a.k.a. "YACC")</a></li>
 <li><a href="https://marketplace.atlassian.com/apps/1217635/control-freak-for-bitbucket-server?hosting=server&amp;tab=overview" rel="nofollow noreferrer">Control Freak</a></li>
 </ul>
</blockquote>

blocks|key|1107029|text|在比特桶云上|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1107030|转到Bitbucket回购->设置->链接|ordered-list-item|1107031|打开“提交消息中的要求问题键”|1107032|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|K|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|L|8|@]|9|@]|A|$]]]|H|$]]

on the Bitbucket cloud

<ol>
<li>go to your Bitbucket repo -> settings -> Links</li>
<li>turn on the "Require issue keys in commit messages"</li>
</ol>

I am trying to block a GIT commit if the commit message doesn't include a JIRA ticket number. Has anyone been able to do this?

From my understanding the following commit message will log the commit message on ticket <code>WEBSITE-4</code>.

<pre><code>JIRA:WEBSITE-4 #comment Testing smart commit.
</code></pre>

But I need a way to block the commit from happening whenever the user forgets to include <code>JIRA:&lt;ticket number&gt;</code> in the commit message.

JIRA smart commit - Block git commit without JIRA ticket number

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

如果提交消息不包括JIRA票证编号，我将尝试阻止GIT提交。有人能做到吗？根据我的理解，下面的提交消息将在票证WEBSITE-4上记录提交消息。JIRA:WEBSITE-4 #comment Testing smart commit.但是，当用户忘记在提交消息中包含JIRA:<ticket number>时，我需要一种阻止提交发生的方法。

问JIRA智能提交-没有JIRA票证号的块git提交
EN

回答 2

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问JIRA智能提交-没有JIRA票证号的块git提交EN

回答 2

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问JIRA智能提交-没有JIRA票证号的块git提交
EN