forgejo/.release-notes-assistant.yaml

categorize: './release-notes-assistant.sh'
branch-development: 'forgejo'
branch-pattern: 'v*/forgejo'
branch-find-version: 'v(?P<version>\d+\.\d+)/forgejo'
branch-to-version: '${version}.0'
branch-from-version: 'v%[1]d.%[2]d/forgejo'
tag-from-version: 'v%[1]d.%[2]d.%[3]d'
branch-known:
  - 'v7.0/forgejo'
cleanup-line: 'sed -Ee "s/^(feat|fix):\s*//g" -e "s;\[(UI|BUG|FEAT|v.*?/forgejo)\]\s*;;g"'
render-header: |

  ## Draft release notes
comment: |
  <details>
  <summary>Where does that come from?</summary>
  The following is a preview of the release notes for this pull request, as they will appear in the upcoming release. They are derived from the content of the `%[2]s/%[3]s.md` file, if it exists, or the title of the pull request. They were also added at the bottom of the description of this pull request for easier reference.

  This message and the release notes originate from a call to the [release-notes-assistant](https://code.forgejo.org/forgejo/release-notes-assistant).
  </details>

  %[1]s
tests: update the PR description with the release notes draft If the 'worth a release-note' label is set, add a release note entry to the description of the pull request as a preview. * use the `release-notes/<pr-number>.md` file if any * otherwise use the pull request title Refs: https://code.forgejo.org/forgejo/release-notes-assistant 2024-07-21 19:05:08 +00:00			`categorize: './release-notes-assistant.sh'`
			`branch-development: 'forgejo'`
			`branch-pattern: 'v*/forgejo'`
			`branch-find-version: 'v(?P<version>\d+\.\d+)/forgejo'`
			`branch-to-version: '${version}.0'`
			`branch-from-version: 'v%[1]d.%[2]d/forgejo'`
			`tag-from-version: 'v%[1]d.%[2]d.%[3]d'`
			`branch-known:`
			`- 'v7.0/forgejo'`
fix(release-notes-assistant): upgrade to always insert a newline * 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 2024-07-23 11:51:32 +00:00			`cleanup-line: 'sed -Ee "s/^(feat\|fix):\s//g" -e "s;\[(UI\|BUG\|FEAT\|v.?/forgejo)\]\s*;;g"'`
tests: update the PR description with the release notes draft If the 'worth a release-note' label is set, add a release note entry to the description of the pull request as a preview. * use the `release-notes/<pr-number>.md` file if any * otherwise use the pull request title Refs: https://code.forgejo.org/forgejo/release-notes-assistant 2024-07-21 19:05:08 +00:00			`render-header: \|`

			`## Draft release notes`
			`comment: \|`
			`<details>`
			`<summary>Where does that come from?</summary>`
			The following is a preview of the release notes for this pull request, as they will appear in the upcoming release. They are derived from the content of the `%[2]s/%[3]s.md` file, if it exists, or the title of the pull request. They were also added at the bottom of the description of this pull request for easier reference.

			`This message and the release notes originate from a call to the [release-notes-assistant](https://code.forgejo.org/forgejo/release-notes-assistant).`
			`</details>`

			`%[1]s`