Skip to content

Latest commit

 

History

History
57 lines (32 loc) · 1.94 KB

CONTRIBUTING.md

File metadata and controls

57 lines (32 loc) · 1.94 KB
Raw

How to Contribute

content-range is a small project, very simple to contribute.

Code of Conduct

We expect project participants to adhere to our Code of Conduct. Please read the full text so that you can understand what actions will and will not be tolerated.

Open Development

All work on content-range happens directly on GitHub. Both core team members and external contributors send pull requests which go through the same review process.

Workflow and Pull Requests

Before submitting a pull request, please make sure the following is done…

  1. Fork the repo and create your branch from master. A guide on how to fork a repository: https://help.github.com/articles/fork-a-repo/

    Open terminal (e.g. Terminal, iTerm, Git Bash or Git Shell) and type:

    $ git clone https://github.com/<your_username>/content-range
$ cd content-range
$ git checkout -b my_branch

    Note: Replace <your_username> with your GitHub username

  2. Run npm install.

  3. If you've added code that should be tested, add tests.

  4. If you've changed APIs, update the documentation.

  5. Ensure the test suite passes via npm test.

    $ npm test

Bugs

Where to Find Known Issues

We will be using GitHub Issues for our public bugs. We will keep a close eye on this and try to make it clear when we have an internal fix in progress. Before filing a new issue, try to make sure your problem doesn't already exist.

Reporting New Issues

The best way to get your bug fixed is to provide a reduced test case. Please provide a public repository with a runnable example.

Code Conventions

This project uses Prettier.

License

By contributing to this project, you agree that your contributions will be licensed under its MIT license.