Skip to content

Latest commit

 

History

History
61 lines (40 loc) · 3.04 KB

CONTRIBUTING.md

File metadata and controls

61 lines (40 loc) · 3.04 KB
Raw

How to contribute

Please note that this project is released with a [Contributor Code of Conduct][code_of_conduct.md]. By participating in this project you agree to abide by its terms.

Creating an Issue

Before you create a new Issue:

  1. Please make sure there is no open issue yet.
  2. If it is a bug report, include the steps to reproduce the issue and please create a reproducible test case on runkit.com. Example: https://runkit.com/gr2m/5aa034f1440b420012a6eebf
  3. If it is a feature request, please share the motivation for the new feature, what alternatives you tried, and how you would implement it.
  4. Please include links to the corresponding github documentation.

Setup the repository locally

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

Submitting the Pull Request

  • Create a new branch locally.
  • Make your changes in that branch to your fork repository
  • Submit a pull request from your topic branch to the main branch on the octokit/plugin-paginate-rest.js repository.
  • Be sure to tag any issues your pull request is taking care of / contributing to. Adding "Closes #123" to a pull request description will automatically close the issue once the pull request is merged in.

Testing a pull request from github repo locally:

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

Merging the Pull Request & releasing a new version

Releases are automated using semantic-release. The following commit message conventions determine which version is released:

  1. fix: ... or fix(scope name): ... prefix in subject: bumps fix version, e.g. 1.2.3 → 1.2.4
  2. feat: ... or feat(scope name): ... prefix in subject: bumps feature version, e.g. 1.2.3 → 1.3.0
  3. 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.

Before the publish it runs the npm run build script which creates a pkg/ folder with distributions for browsers, node and Typescript definitions. The contents of the pkg/ folder are published to the npm registry.

If the pull request looks good but does not follow the commit conventions, use the Squash & merge button.