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.
Customising the output: --context, --writerOpts, --parserOpts, and the command line
See original GitHub issueHi,
I’ve been extensively reading the various issues and repos relative to this project and though you indicate clearly that one should be able to customise the transform to output more types than the default ones, and even if the writer documentation states that I can use an object for the transform key, I can’t even start to think of the beginning of an idea of what my CLI options would look like.
Can you provide an example about how to change the output types with the CLI, please? Or, if not possible, a quick gist on how to do it programmatically, maybe?
On a broader scale, having a thorough example about the possible options would be amazing, but it’s a lot more work, admittedly.
Thank you for the project and your help.
Issue Analytics
- State:
- Created 8 years ago
- Comments:12 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Closing for lack of actual help. Got it working with https://github.com/rafinskipg/git-changelog meanwhile.
How am I not helping you? I answered all your questions. You don’t need to go through issues to find out how to use the tool. The readme is supposed to be enough. If not, send a PR to improve it. You only said you want to select which types of commits get output to the CHANGELOG, this is extremely vague, what do you really mean select which type? and all options are already written in the docs.