Pact-JS is built and maintained by developers like you, and we appreciate contributions very much. You are awesome!
Here is a short checklist to give your PR the best start:
Everything above can be removed once checked
[x] npm run dist works locally (this will run tests, lint and build)
[x] Commit messages are ready to go in the changelog (see below for details)
[x] PR template filled in (see below for details)
Commit messages
Our changelog is automatically built from our commit history, using conventional changelog. This means we'd like to take care that:
commit messages with the prefix fix: or fix(foo): are suitable to be added to the changelog under "Fixes and improvements"
commit messages with the prefix feat: or feat(foo): are suitable to be added to the changelog under "New features"
If you've made many commits that don't adhere to this style, we recommend squashing
your commits to a new branch before making a PR. Alternatively, we can do a squash
merge, but you'll lose attribution for your change.
For more information please see CONTRIBUTING.md
Everything above can be removed
PR Template
Please describe what this PR is for, or link the issue that this PR fixes
Came across this issue mention here
You may add as much or as little context as you like here, whatever you think is right
I choose little.
Thanks Haz - yes, I merged a bunch of dependabot PRs the other day and Nest JS isn't happy (see #1010). This change looks good though, appreciate it :)
Thank you for making a pull request!
Pact-JS is built and maintained by developers like you, and we appreciate contributions very much. You are awesome!
Here is a short checklist to give your PR the best start:
Everything above can be removed once checked
npm run dist
works locally (this will run tests, lint and build)Commit messages
Our changelog is automatically built from our commit history, using conventional changelog. This means we'd like to take care that:
fix:
orfix(foo):
are suitable to be added to the changelog under "Fixes and improvements"feat:
orfeat(foo):
are suitable to be added to the changelog under "New features"If you've made many commits that don't adhere to this style, we recommend squashing your commits to a new branch before making a PR. Alternatively, we can do a squash merge, but you'll lose attribution for your change.
For more information please see CONTRIBUTING.md
Everything above can be removed
PR Template
Please describe what this PR is for, or link the issue that this PR fixes Came across this issue mention here
You may add as much or as little context as you like here, whatever you think is right I choose little.
Thanks again! You're welcome