Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.
Before you create a new Issue:
First, fork the repository.
Setup the repository locally. Replace <your account name>
with the name of the account you forked to.
git clone https://github.com/<your account name>/plugin-paginate-rest.js.git cd plugin-paginate-rest.js npm install
Run the tests before making changes to make sure the local setup is working as expected
npm test
octokit/plugin-paginate-rest.js
repository.You can install @octokit/plugin-paginate-rest
from each pull request. Replace [PULL REQUEST NUMBER]
Once you are done testing, you can revert back to the default module @octokit/plugin-paginate-rest
from npm with npm install @octokit/plugin-paginate-rest
Releases are automated using semantic-release. The following commit message conventions determine which version is released:
fix: ...
or fix(scope name): ...
prefix in subject: bumps fix version, e.g. 1.2.3
→ 1.2.4
feat: ...
or feat(scope name): ...
prefix in subject: bumps feature version, e.g. 1.2.3
→ 1.3.0
BREAKING CHANGE:
in body: bumps breaking version, e.g. 1.2.3
→ 2.0.0
Only one version number is bumped at a time, the highest version change trumps the others. Besides publishing a new version to npm, semantic-release also creates a git tag and release on GitHub, generates changelogs from the commit messages and puts them into the release notes. s If the pull request looks good but does not follow the commit conventions, use the Squash & merge button.