Julian Tölle 0ae2d909bc fix: use commits with slightly invalid messages in release notes (#105) ... Fixes a bug where commits with messages that do not strictly conform to conventional commits spec would be ignored. This could easily happen while parsing footers like "Closes #xx" which would start the footer section, while continuing with the body afterwards. This solution has two downsides: - these warnings are not surfaced to the user. - If a `BREAKING CHANGE` footer exists after the parsing issue it is ignored Co-authored-by: jo <ljonas@riseup.net>		2024-11-15 17:25:15 +01:00
..
changelog	feat(changelog): omit version heading in forge release notes	2024-09-22 14:00:30 +02:00
commitparser	fix: use commits with slightly invalid messages in release notes (#105)	2024-11-15 17:25:15 +01:00
forge	deps: update module github.com/google/go-github/v65 to v66 (#103)	2024-11-15 15:10:52 +01:00
git	refactor: move things to packages (#39)	2024-08-31 15:23:21 +02:00
markdown	feat: edit commit message after merging through PR (#43)	2024-09-06 23:17:06 +02:00
pointer	refactor: move things to packages (#39)	2024-08-31 15:23:21 +02:00
releasepr	refactor: labels as structs with descriptions (#46)	2024-09-07 21:33:28 +02:00
updater	refactor: move things to packages (#39)	2024-08-31 15:23:21 +02:00
versioning	refactor: move things to packages (#39)	2024-08-31 15:23:21 +02:00