6 commits

Author	SHA1	Message	Date
Earl Warren	f586944db3	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.	2024-10-22 06:54:27 +02:00
Twenty Panda	b85ec067ca	feat(release-notes-assistant): diff of the change in preview	2024-07-25 22:32:14 +02:00
Earl Warren	ba006b2eef	fix(release-notes-assistant): ignore WIP prefixes	2024-07-24 16:49:21 +02:00
Twenty Panda	80a1461e7d	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 13:53:46 +02:00
Twenty Panda	043214d751	fix(release-notes-assistant): be more conservative when cleaning up ... Do not replace http*: it breaks URLs.	2024-07-23 11:37:40 +02:00
Twenty Panda	5c734d8885	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-23 09:27:43 +02:00