首页
学习
活动
专区
圈层
工具
发布
社区首页 >问答首页 >如果没有找到提交关键字,强制版本凸点(补丁)

如果没有找到提交关键字,强制版本凸点(补丁)
EN

Stack Overflow用户
提问于 2022-11-02 17:03:01
回答 1查看 37关注 0票数 1

我有一些团队与我一起工作,我喜欢语义发布,但是开发人员经常忘记将提交消息关键字放入其中(例如,fix、feat、perf)。我知道这是我们需要敲击的东西,或者实现一个预提交钩子来要求它。https://semantic-release.gitbook.io/semantic-release/#commit-message-format

如果在PR合并中没有提供特殊的提交关键字,或者提交到我使用语义发布监视的分支,那么是否有任何方法可以将语义发布配置为总是增加我的补丁版本号。

例如:团队分支的主要创建特性-分支-a和迭代一天与一些小的变化。他们为上述分支机构创建PR-1拉请求。他们忘记包括提交关键字(修复,专长,perf等),然后他们合并PR到main。语义发布是针对主分支的,不会削减新版本.我希望能够告诉语义发布至少总是增加补丁版本,并创建一个github版本。

我尝试了下面的配置,但没有成功:

代码语言:javascript
复制
{
    "branches": [
      "main", 
      {"name": "dev", "prerelease": true}
    ], 
    "plugins": [
      ["@semantic-release/commit-analyzer", {
        "preset": "angular",
        "releaseRules": [
          {
            "subject": "*",
            "release": "patch"
          },
          {
            "subject": "fix*",
            "release": "patch"
          },
          {
            "subject": "feat*",
            "release": "minor"
          },
          {
            "subject": "perf*",
            "release": "major"
          }
        ]
      }],
      
      "@semantic-release/release-notes-generator",
      [
        "@semantic-release/github"
      ]
    ]
  }

日志输出(没有新版本的补丁颠簸):

代码语言:javascript
复制
[5:00:26 PM] [semantic-release] › ℹ  Found git tag v1.2.3 associated with version 1.2.3 on branch main
[5:00:26 PM] [semantic-release] › ℹ  Found 2 commits since last release
[5:00:26 PM] [semantic-release] › ℹ  Start step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[5:00:26 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: test
[5:00:26 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[5:00:26 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: test
[5:00:26 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[5:00:26 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analysis of 2 commits complete: no release
[5:00:26 PM] [semantic-release] › ✔  Completed step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[5:00:26 PM] [semantic-release] › ℹ  Start step "analyzeCommits" of plugin "@semantic-release/exec"
[5:00:26 PM] [semantic-release] › ✔  Completed step "analyzeCommits" of plugin "@semantic-release/exec"
[5:00:26 PM] [semantic-release] › ℹ  There are no relevant changes, so no new version is released.

更新:想出了如何通过这个问题- https://github.com/semantic-release/semantic-release/discussions/1819

谢谢!

EN

回答 1

Stack Overflow用户

发布于 2022-11-02 17:48:07

https://github.com/semantic-release/semantic-release/discussions/1819

{“消息”:"*",“发布”:“修补程序”}

票数 0
EN
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://stackoverflow.com/questions/74293068

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档