Skip to content

How-To-Contribute.md

Latest commit

 

History

History
17 lines (9 loc) · 2.78 KB

How-To-Contribute.md

File metadata and controls

17 lines (9 loc) · 2.78 KB

Note: For First Bug, go straight to step 4. Join the Slack team by following through the How to Volunteer. All types of contributions are welcome. 😄

  1. Familiarize yourself with the contributor code of conduct to have an effective contributor experience. Join the Slack team by following through the How to Volunteer.

  2. Fork the HTML5 Hackform Tool repo by clicking on the "Fork" button at the top right-hand side of the repo and find a bug (e.g. code, documentation, accessibility, test coverage) or think of a quick question. For questions that require more lengthy discussions, join the Slack team.

  3. Raise an issue by indicating a title for the new issue (the numbering of the issue with e.g. #1, #2, #3, #4, etc. is automatically generated), what the issue is, why is it an issue, what needs improvement or fixing, and what can be done to improve or fix it. Label the issue (e.g. bug, documentation, accessibility, test coverage). See Raise Issue Template

  4. Work on the improvement or fixture of each issue on a separate branch (label branch using issue number) and send a pull request for review, comparing a new head branch of modifications with the base branch by selecting the associated issue number as the new head branch with the pull request. The issue number selected will be the title of the pull request. The commit message will contain reference to the issue number, the changes made, and the test plan (if any). The pull request will be labelled as high priority for easy fixes, medium priority for middle-of-the-road fixes, and low priorty for difficult fixes. See Send Pull Request Template

  5. Upon pull request review approval by the author or maintainers, status checks will be carried out. Pull request reviews are carried out in order of priority, with those labelled as high priority (easy fix) being reviewed before the medium priority (middle-of-the-road fix) and the low priority (difficult fix) pull requests.

  6. Upon passing the status checks, the improvement or fixture will be merged with the master branch and the issue will be closed by the author or maintainers.

  7. Thanks for your invaluable contribution. ❤️

  8. Your username will appear on the #walloffame on Slack. 👑