Skip to content

Latest commit

 

History

History
86 lines (61 loc) · 3.65 KB

CONTRIBUTING.md

File metadata and controls

86 lines (61 loc) · 3.65 KB

Contributing

Thanks for being willing to contribute!

Working on your first Pull Request? You can learn how from this free series How to Contribute to an Open Source Project on GitHub

Project setup

  1. Fork and clone the repo
  2. $ npm install to install dependencies
  3. $ npm start validate to validate you've got it working
  4. Create a branch for your PR

This project uses nps and you can run npm start to see what scripts are available.

Add an example

Is the example just a code snippet or is it a full fledged project? If it is a code snippet, go ahead and add it to our examples readme file If it is an example that requires you to create a new, albeit, mini-project, here are the steps to add it.

  • Create a new folder inside our examples folder.
  • Name it to describe what your example is about.
  • You can create a new npm/yarn setup inside this folder.
  • Don't forget to add a readme.md inside your example folder.
  • Now add the commands to validate and build your example project to our package-scripts.
  • Navigate to the package-scripts.js and the examples command.
  • Add a new command specific to your example folder.
  • Here, you can provide the scripts that need to be run to validate and build your folder. Use the awesome nps, which has a ton of utilities to help you.
  • Run npm start examples to make sure all your setup is correct.

You should have a great example running on glamorous by now. Go ahead and submit a PR! Also you can refer to the existing example at with-jest

Add yourself as a contributor

This project follows the all contributors specification. To add yourself to the table of contributors on the README.md, please use the automated script as part of your PR:

npm start "contributors.add"

Follow the prompt. If you've already added yourself to the list and are making a new type of contribution, you can run it again and select the added contribution type.

Committing and Pushing changes

This project uses semantic-release to do automatic releases and generate a changelog based on the commit history. So we follow a convention for commit messages. Please follow this convention for your commit messages.

You can use commitizen to help you to follow the convention

Once you are ready to commit the changes, please use the below commands

  1. git add <files to be committed>
  2. $ npm start commit

... and follow the instruction of the interactive prompt.

opt into git hooks

There are git hooks set up with this project that are automatically installed when you install dependencies. They're really handy, but are turned off by default (so as to not hinder new contributors). You can opt into these by creating a file called .opt-in at the root of the project and putting this inside:

commit-msg
pre-commit

Help needed

Please checkout the ROADMAP.md and raise an issue to discuss any of the items in the want to do or might do list.

Also, please watch the repo and respond to questions/bug reports/feature requests! Thanks!