From f586944db3b66119539d9d6b87f362d779ae47e4 Mon Sep 17 00:00:00 2001 From: Earl Warren Date: Tue, 22 Oct 2024 06:54:27 +0200 Subject: [PATCH] chore(release-notes): no need to specify they are draft Since they are written to the milestone that is still open, there is no risk of confusing them with final release notes. Such a distinction is more relevant when in the context of a release notes file committed to the repository. --- .release-notes-assistant.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.release-notes-assistant.yaml b/.release-notes-assistant.yaml index 15c73f9b39..b3e5a8e665 100644 --- a/.release-notes-assistant.yaml +++ b/.release-notes-assistant.yaml @@ -10,7 +10,7 @@ branch-known: cleanup-line: 'sed -Ee "s/^(feat|fix):\s*//g" -e "s/^\[WIP\] //" -e "s/^WIP: //" -e "s;\[(UI|BUG|FEAT|v.*?/forgejo)\]\s*;;g"' render-header: | - ## Draft release notes + ## Release notes comment: |
Where does that come from?