-
Notifications
You must be signed in to change notification settings - Fork 225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"tools/changelog-helper.sh group-entries" grouping improvement suggestions #3319
Comments
@softins is this something you could look at? |
All this processing is currently done using
This I have done quite easily by adding a suitable entry to the list of categories.
I have added another entry to the categories, to collect all these entries together, but they are still individual. Merging them is too complex to do with
Again, I've added category to collect these together, but merging them is a lot more complex without a rewrite. Currently there is only one such entry since 3.11.0.
Sorting is currently done by initial string after the leading |
The grouping will make manual post-processing much easier, anyway! |
What is the current behaviour and why should it be changed?
The current sorting method means "Client:" and "Client/Server:" tagged entries can be mixed:
Ideally the grouping would keep all "Client:" entries together, all "Client/Server:" entries together (following "Client:") and all "Server:" entries together (following any "Client/Server:" entries).
Currently, each PR for Weblate gets a separate entry. Grouping should merge "Translations updated from Hosted Weblate" by "@weblate" into a single entry listing all the PR numbers
Currently, "Build:" entry sorting isn't done and grouping could be improved. For example:
It would be nice if there was a single "Build: Updated bundled Qt6" entry with "- versions 6.6.0, 6.6.1, 6.6.3" by "@app/github-actions".
Sorting and grouping all the "@app/github-actions" and "@app/dependabot" updates together like this would condense the change log significantly (reducing manual editing).
The text was updated successfully, but these errors were encountered: