forks/forgejo
1
0
Fork 0
Code Releases Activity

fix(release-notes-assistant): upgrade to always insert a newline

Browse source 
* if <!-- is inserted just after a <!-- --> it will not render
  well, it needs to be separated by a newline
* do not use ? in sed -E, it is not the same as with JavaScript
This commit is contained in:
Twenty Panda 2024-07-23 13:51:32 +02:00
parent 043214d751
commit 80a1461e7d
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
.forgejo/workflows/release-notes-assistant.yml
View file

@ -28,4 +28,4 @@ jobs:
- name: release-notes-assistant preview - name: release-notes-assistant preview
run: | run: |
go run code.forgejo.org/forgejo/release-notes-assistant@v1.0.0 --config .release-notes-assistant.yaml --storage pr --storage-location ${{ github.event.pull_request.number }} --forgejo-url $GITHUB_SERVER_URL --repository $GITHUB_REPOSITORY --token ${{ secrets.RELEASE_NOTES_ASSISTANT_TOKEN }} preview ${{ github.event.pull_request.number }} go run code.forgejo.org/forgejo/release-notes-assistant@v1.0.1 --config .release-notes-assistant.yaml --storage pr --storage-location ${{ github.event.pull_request.number }} --forgejo-url $GITHUB_SERVER_URL --repository $GITHUB_REPOSITORY --token ${{ secrets.RELEASE_NOTES_ASSISTANT_TOKEN }} preview ${{ github.event.pull_request.number }}

2
.release-notes-assistant.yaml
View file

@ -7,7 +7,7 @@ branch-from-version: 'v%[1]d.%[2]d/forgejo'
tag-from-version: 'v%[1]d.%[2]d.%[3]d' tag-from-version: 'v%[1]d.%[2]d.%[3]d'
branch-known: branch-known:
- 'v7.0/forgejo' - 'v7.0/forgejo'
cleanup-line: 'sed -Ee "s/^(feat|fix).*?:\s*//g" -e "s;\[(UI|BUG|FEAT|v.*?/forgejo)\]\s*;;g"' cleanup-line: 'sed -Ee "s/^(feat|fix):\s*//g" -e "s;\[(UI|BUG|FEAT|v.*?/forgejo)\]\s*;;g"'
render-header: | render-header: |
## Draft release notes ## Draft release notes