mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2024-11-25 14:35:40 +00:00
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:
parent
e45c304b31
commit
f586944db3
|
@ -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>
|
||||||
|
|
Loading…
Reference in a new issue