fix(pr-followup): PR #716 comment 3330228890 — **<sub><sub>
…https://img.shields.io/badge… Disposition: fixed Source: #716 (comment) Path: scripts/generate_changelog_entry.py
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fc82b57588
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| if any( | ||
| _tree_entry_at(source, commit_hash, path) != _tree_entry_at(source, since_ref, path) | ||
| for path in relevant_paths |
There was a problem hiding this comment.
When a previous squash release contained multiple conventional commits touching the same file, and the next patch also edits that file, this comparison can still re-include older released subjects. For example, if develop had feat changing f.txt to A, then fix changing it to A+B, main squash-merged A+B, and the new patch changes f.txt to A+B+C, the first old commit's tree entry (A) differs from main (A+B), so it is incorrectly selected for the new changelog even though it was already released.
Useful? React with 👍 / 👎.
1 participant
Disposition: fixed
Source: #716 (comment)
Path: scripts/generate_changelog_entry.py