You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

66 lines
2.6 KiB

4 years ago
  1. # :eight_spoked_asterisk: :stars: :sparkles: :dizzy: :star2: :star2: :sparkles: :dizzy: :star2: :star2: Contributing :star: :star2: :dizzy: :sparkles: :star: :star2: :dizzy: :sparkles: :stars: :eight_spoked_asterisk:
  2. So, you want to contribute to this project! That's awesome. However, before
  3. doing so, please read the following simple steps how to contribute. This will
  4. make the life easier and will avoid wasting time on things which are not
  5. requested. :sparkles:
  6. ## Discuss the changes before doing them
  7. - First of all, open an issue in the repository, using the [bug tracker][1],
  8. describing the contribution you would like to make, the bug you found or any
  9. other ideas you have. This will help us to get you started on the right
  10. foot.
  11. - If it makes sense, add the platform and software information (e.g. operating
  12. system, Node.JS version etc.), screenshots (so we can see what you are
  13. seeing).
  14. - It is recommended to wait for feedback before continuing to next steps.
  15. However, if the issue is clear (e.g. a typo) and the fix is simple, you can
  16. continue and fix it.
  17. ## Fixing issues
  18. - Fork the project in your account and create a branch with your fix:
  19. `some-great-feature` or `some-issue-fix`.
  20. - Commit your changes in that branch, writing the code following the
  21. [code style][2]. If the project contains tests (generally, the `test`
  22. directory), you are encouraged to add a test as well. :memo:
  23. - If the project contains a `package.json` or a `bower.json` file add yourself
  24. in the `contributors` array (or `authors` in the case of `bower.json`;
  25. if the array does not exist, create it):
  26. ```json
  27. {
  28. "contributors": [
  29. "Your Name <and@email.address> (http://your.website)"
  30. ]
  31. }
  32. ```
  33. ## Creating a pull request
  34. - Open a pull request, and reference the initial issue in the pull request
  35. message (e.g. *fixes #<your-issue-number>*). Write a good description and
  36. title, so everybody will know what is fixed/improved.
  37. - If it makes sense, add screenshots, gifs etc., so it is easier to see what
  38. is going on.
  39. ## Wait for feedback
  40. Before accepting your contributions, we will review them. You may get feedback
  41. about what should be fixed in your modified code. If so, just keep committing
  42. in your branch and the pull request will be updated automatically.
  43. ## Everyone is happy!
  44. Finally, your contributions will be merged, and everyone will be happy! :smile:
  45. Contributions are more than welcome!
  46. Thanks! :sweat_smile:
  47. [1]: https://github.com/Bloggify/github-calendar/issues
  48. [2]: https://github.com/IonicaBizau/code-style