Investigate how modified changelogs work in release process
Open
domain: release automation
- Dominant language
- JavaScript
- Stars
- 77
- Forks
- 83
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 37
Description
When a changelog is created by the tooling and then is modified by the user before usage in a release, the changes are not include/brought back to the Github Release/"cherry-pick".
This issue was brought up for discussion in https://github.com/angular/dev-infra/pull/260 but is being considered in a separate scope.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the release tooling and the discussion in pull request 260. Trace how a tooling-created changelog is handled after a user edits it, and document what must change so those edits reach the GitHub Release or cherry-pick.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100