Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

How to restructure Release Drafter output by component first, then by type?#1443

Unanswered
pohanhuangtw asked this question inQ&A
Discussion options

Hi all,

I'm currently using Release Drafter to generate changelogs with atype-first layout, where sections are grouped by labels likekind/feature,kind/bug, etc.

My current output looks like this:

## ⚠️ Breaking changes- [controller] breaking change!: new README## 🚀 Features- [controller] feat: update release- [worker] feat: add auto release## 🐛 Bug Fixes- [storage] fix: update release- [controller] fix: indent to create-release## 🧰 Maintenance- [controller] chore: trigger autolabeler- [controller] fix(deps): update dependencies

What I want instead

I'd like to generate a changelog groupedby component first, then by type, like this:

# Controller## ⚠️ Breaking changes- breaking change!: new README## 🚀 Features- feat: update release## 🐛 Bug Fixes- fix: indent to create-release## 🧰 Maintenance- chore: trigger autolabeler- fix(deps): update dependencies# Worker## 🚀 Features- feat: add auto release# Storage## 🐛 Bug Fixes- fix: update release

My question

Is there a way to configure Release Drafter to achieve this kind ofcomponent-first layout?

I’ve already been labeling PRs with both:

  • component/controller,component/worker, etc.
  • kind/feature,kind/bug,kind/chore, etc.

But Release Drafter only allows grouping by one set of labels at a time (typeor component).
Has anyone found a workaround — such as:

  • clever use ofcategories.title and\n nesting?
  • post-processing the markdown after generation?
  • any Release Drafter plugin / fork that supports hierarchical output?

Thanks in advance for any ideas!

You must be logged in to vote

Replies: 0 comments

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Category
Q&A
Labels
None yet
1 participant
@pohanhuangtw

[8]ページ先頭

©2009-2025 Movatter.jp