Improve deduping of commits (reverts) and for pre-releases
- Dominant language
- JavaScript
- Stars
- 77
- Forks
- 83
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 37
Description
We should dedupe reverts (Andrew K mentioned this in the past -- not sure if we have an issue for it)
Also we should look into improving the deduping for next/FF/RC pre-releases. Commits that also went into patch should not show up again. We have good deduping for other scenarios but our release notes compare range deduping is not ideal for pre-releases because we only compare to the previous pre-release, but should also dedupe anything that is part of the patch branch already.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the release-notes compare-range deduping logic and trace how it handles reverts and next/FF/RC pre-releases. Done means reverts are deduplicated and commits already included in the patch branch do not appear again in pre-release notes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100