mirrors
/
forgejo
mirror of
1
Fork 0
Code Issues Releases Activity

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.
This commit is contained in:
Earl Warren 2024-10-22 06:54:27 +02:00
parent e45c304b31
commit f586944db3
No known key found for this signature in database
GPG Key ID: 0579CB2928A78A00
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.release-notes-assistant.yaml
View File

@ -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"' 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: | render-header: |
## Draft release notes ## Release notes
comment: | comment: |
<details> <details>
<summary>Where does that come from?</summary> <summary>Where does that come from?</summary>