Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

noisy output when "fixes #" syntax used in pull request

See original GitHub issue

The output of the CHANGELOG template is pretty noisy when someone specifies that a pull request closes issues (see https://github.com/istanbuljs/babel-plugin-istanbul/blob/master/CHANGELOG.md#bug-fixes).

take realpath of process.cwd(), fixes #7 (#8) (e8d3785), closes #7 #8

Maybe if we moved (#8) (e8d3785) to the end of the line? not quite sure what would make this read better.

thoughts? @nexdrew, @Tapppi, @stevemao

Issue Analytics

State:
Created 7 years ago
Reactions:1
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

nexdrewcommented, Jul 10, 2016

The Angular convention existed before GitHub’s squash-and-merge feature, but the squash-and-merge is really what makes standard-version compelling. I think this tool should work best with the defaults used by squash-and-merge rather than exact Angular compliance.

0reactions

stevemaocommented, Jul 10, 2016

Maybe not. TBH I don’t like to hardcode the verb closes, it should use the same verb in the commit message (so it could be fixes, resolves etc).