nodejs / nodejs/changelog-maker
Has weird issues when trying to get changes based on refs.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 236
- Forks
- 41
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 7
Description
Sometimes it will drop commits, add to many commits, not get anything at all, etc, when using --start-ref= and/or --end-ref= on io.js.
For example, to get the commits in https://github.com/iojs/io.js/issues/1383#issuecomment-91247024 I ran changelog-maker --start-ref=b8310cb --end-ref=08e89b1 iojs io.js, but it gets commits well before b8310cb also.
(This is the same issue I had trying to use this to make the 1.6.4 release before it was properly re-tagged.)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the changelog-maker command with the reported --start-ref and --end-ref values against io.js. Trace how the CLI resolves refs and selects commits, then verify that the resulting range contains exactly the commits between the two refs without dropped or extra commits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100