Merged PR linked to an issue that isn't closed?...
- Dominant language
- Go
- Stars
- 65
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
It is common to have an issue represent the total work to be done and split up that work across multiple PRs. In this case there would be a merged PR with an issue that is still open. When we detect this case, what should we do? Report out the partial feature based on the PR information? Hold back from reporting the entry in the changelog since the issue isn't closed? Or something else.
(My preference is to hold of from including it in the changelog until the linked issue is closed, but was curious for other thoughts here)
Contributor guide
Research direction
No files, tests, or entry points are named. Start by reviewing how the changelog generator handles linked pull requests and open issues, then decide whether an open issue should suppress reporting; done requires an agreed behavior and corresponding implementation and tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, go
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100