Skip to content

Latest commit

 

History

History
25 lines (19 loc) · 2.1 KB

CONTRIBUTE.md

File metadata and controls

25 lines (19 loc) · 2.1 KB
Raw

Contributor guidelines

What do I need to know to help?

If you are looking to help to with a code contribution our project uses TypeScript, Webpack and Gulp. If you don't feel ready to make a code contribution yet, no problem! You can also check out the documentation issues.

How do I make a contribution?

Never made an open source contribution before? Wondering how contributions work in the in our project? Here's a quick rundown!

  • Find an issue that you are interested in addressing or a feature that you would like to add.
  • Fork the repository associated with the issue to your local GitHub organization. This means that you will have a copy of the repository under your-GitHub-username/phnum-js.
  • Clone the repository to your local machine using git clone https://github.com/github-username/phnum-js.git.
  • Create a new branch for your fix using git checkout -b branch-name.
  • Make the appropriate changes for the issue you are trying to address or the feature that you want to add.
  • Use git add paths-of-changed-files to add the file contents of the changed files to git.
  • Use git commit -m "A short message of the changes made" to commit your changes with a descriptive message.
  • Push the changes to the remote repository using git push origin branch-name.
  • Submit a pull request to the upstream repository.
  • Title the pull request with a short description of the changes made and the issue or bug number associated with your change. For example, you can title an issue like so "Added more log outputting to resolve #1234".
  • In the description of the pull request, explain the changes that you made, any issues you think exist with the pull request you made, and any questions you have for the maintainer. It's OK if your pull request is not perfect (no pull request is), the reviewer will be able to help you fix any problems and improve it!
  • Wait for the pull request to be reviewed by a maintainer.
  • Make changes to the pull request if the reviewing maintainer recommends them.
  • Celebrate your success after your pull request is merged!