Open duckinator opened 9 months ago
Yes, relevant_to_changelog
relies on a (strict) comparison of merge time and release time, as reported by Github's API.
I think the ideal solution would be to use the actual git history (or some API which exposes info from it) as this would be a lot more robust, even in cases where multiple release branches exist etc.
e.g., v7.0.1 includes the PR for merging v7.0.0:
but this is in spite of the fact that the PR is included in the info for v7.0.0:
v7.0.0 also included the PR for the v6.0.1 release.
The relevant code is probably
bork.github_api.GithubApi._relevant_to_changelog()
.