Skip to content
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

Changelog generation: Avoid false positives #2657

Closed
hoffie opened this issue Jun 18, 2022 · 0 comments · Fixed by #2661
Closed

Changelog generation: Avoid false positives #2657

hoffie opened this issue Jun 18, 2022 · 0 comments · Fixed by #2661
Milestone

Comments

@hoffie
Copy link
Member

hoffie commented Jun 18, 2022

The changelog generator added #1873 for the latest nightly, although it was already part of a previous release.

It was probably due to 0764536.
The generator looks as both Github milestones and git history. Maybe the latter should always be cross-checked to remove PRs which are properly assigned to a previous milestone.

hoffie added a commit to hoffie/jamulus that referenced this issue Jun 18, 2022
… in git log

Previously, all PRs from the relevant git log were added to the
ChangeLog. This causes false positives when older PRs are intentionally
mentioned again (e.g. for further fixes or documentation updates).
At the same time, simply skipping them removes an additional method to
avoid forgotten PRs.

Therefore, only add git-mentioned PRs if they don't have a milestone (or
a matching one).

Fixes: jamulussoftware#2657
@hoffie hoffie added this to the Release 3.9.0 milestone Jun 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant