mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2024-11-08 18:04:14 +01:00
1171069ced
It is not for the developer to keep them sorted in a hierarchy when the release they belong to can be deduced from the tag of the release into which they were merged. The release notes assistant does that work instead. Some files appeared in more than one directory (feat and fix for instance) when the PR contains multiple unrelated commits which is what happens on a regular basis with the weekly cherry-pick of Gitea. Those files were merged into one and each line changed to start with a conventional commit prefix (feat: fix:). Each line in a file will be a separate line in the release notes, they are not groupped together even when they relate to the same PR. The determination of the category in which they should be displayed will be based on regular expressions using either the PR title or the line to add to the release notes itself. Unify the content of each file to either be a bullet list of independent pull requests or be folded into a single line if it is multiline. Multiline content belongs to the documentation. Refs: https://code.forgejo.org/forgejo/release-notes-assistant Refs: https://www.conventionalcommits.org/en/v1.0.0/
849 B
849 B
- feat: API endpoints that return a repository now also include the topics
- feat: Display an error when an issue comment is edited simultaneously by two users instead of silently overriding one of them
- feat: Add support for a credentials chain for minio
- feat: Rename project board into column because it was confusing to users
- feat(perf): improve performances when retrieving pull requests via the API