NPM option parsing improvements and documentation improvements #843
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Warning
This should be merged with "rebase & merge" to retain proper conventional commit history for the changelog generation
Description
Couple of changes bundled:
skip-commit
in cliff-jumper. Because the appropriate syntax forgit-cliff
is--skip-commit SHA --skip-commit SHA --skip-commit SHA --skip-commit SHA <options options>
it is more ideal if the NodeJS code optionally takes an array of commits which can easily be parsed to CLI args in the library as opposed to janking something in cliff-jumper.Options
type so I added them.--gitea-repository
mentioned GitLab and adjusted it accordingly.Motivation and Context
As mentioned above, I got the request to implement
--skip-commit
in cliff-jumper and needed a change for that.How Has This Been Tested?
I ran
yarn build
innpm/git-cliff
thenyarn pack
to create apackage.tgz
which I then installed incliff-jumper
This is when providing an array of strings:
Screenshots / Logs (if applicable)
Types of Changes
Checklist: