0

I've found semantic-release and it looks very useful. But I'm wondering how to customize it to fit our workflow:

  • no dev branch, just a master and feature/fix/chore branches.
  • latest release (github with relevant git tag) correspond to version pushed to production.
  • Draft release correspond to version pushed to staging.

This is a private industry project, so we cannot go completely lean and must respect internal design guidelines including batching PRs on staging before releasing on production.

I can add a dev branch, and push staging from dev, then production from master after merging dev to master. But I'd like my github draft release to be updated as soon as a pull request is merged back into dev (draft release that would become the latest release once dev is merged into master).

Is that somehow possible ? I recently installed the semantic pull request github app, and started using conventional commit conventions, but I'm unclear about how to use release-notes-generator on its own, or whether it handles the github draft release mode.

4

1 回答 1

0

但我想知道如何自定义它以适应我们的工作流程： * 没有 dev 分支，只有 master 和 feature/fix/chore 分支。* 最新版本（带有相关 git 标签的 github）对应于推送到生产的版本。* 草稿版本对应于推送到暂存的版本。

它仅分析您配置的分支上的提交（默认情况下master）。提交如何到达那里并不重要，您可以在它们到达之前将它们合并到您想要的任何分支中master。当他们到达master并运行语义发布时，它将分析提交master并在必要时发布。

语义发布尚不支持草稿/预发布（请参阅https://github.com/semantic-release/semantic-release/issues/563）。

我最近安装了语义拉请求 github 应用程序

你指的是什么？那时还没有语义发布的 GitHub 应用程序，尽管它计划在某个时候有一个（https://github.com/semantic-release/semantic-release/issues/585）。

但我不清楚如何单独使用 release-notes-generator，或者它是否处理 github 草稿发布模式

release-notes-generator负责生成发布说明，不与 GitHub 交互。@semantic-release/github负责在 GitHub 上创建发布。

于 2018-09-19T05:34:14.483 回答