Skip to content

Latest commit

 

History

History
107 lines (75 loc) · 5.73 KB

CONTRIBUTING.md

File metadata and controls

107 lines (75 loc) · 5.73 KB
Raw

🎇Contributing Guidelines

This documentation contains a set of guidelines to help you during the contribution process.

I'm happy to welcome all the contributions from anyone willing to add new scripts to this repository. Thank you for helping out and remember, no contribution is too small.

💻Before Contributing

Welcome to arpitghura/typing-test. Before sending your pull requests, make sure that you read the whole guidelines. If you have any doubts about the contributing guide, please feel free to reach out on Discord

🙌Contribution

Any contribution is accepted, from fixing grammatical mistakes to implementing complex scripts. Please read this section if you are contributing your work.

🔖Steps to Contribute

Following are the steps to guide you:

  • Step 1: Fork into your account
  • Step 2: Clone the repo in your machine using 
    git clone https://github.com/<your_username>/typing-test.git
  • Step 3: Replace the <your_username> with your github username.
  • Step 4: Create your feature branch 
    git checkout -b <feature-name>
  • Step 5: Commit all the changes (Write commit message as "Small Message") 
    git commit -m "Write a meaningful but small commit message"
  • Step 6: Push the changes for review 
    git push origin <branch-name>
  • Step 7: Create a PR on Github. (Don't just hit the create a pull request button, you must write a PR message to clarify why and what are you contributing)

🔨Note:

  • Do not edit/delete someone else's script in this repository. You can only insert new scripts in this repository.
  • Give a meaningful name to whatever file or folder you are adding.
  • To state an example, folder name should be as "Images" and file name should be "front_image.jpg"

🔑Guidelines

  1. Welcome to this repository, if you are here as an open source program participant/contributor.
  2. Participants / contributors have to comment on issues they would like to work on, and mentors or the PA will assign you.
  3. Issues will be assigned on a first-come, first-serve basis.
  4. Participants / Contributors can also open their issues using issue_template, but it needs to be verified and labeled by a mentor or PA. Please discuss this with the team once before opening your issues. We respect all your contributions, whether it is an Issue or a Pull Request.
  5. When you raise a issue, make sure you get it assigned to you, before you start working on that project.
  6. Each participant / contributor will be assigned 1 issue (max) at a time to work.
  7. Participants are expected to follow project guidelines and coding style. Structured code is one of our top priorities.
  8. Try to explain your approach to solve any issue in the comments. This will increase the chances of you being assigned.
  9. Don't create issues that are already listed.
  10. Please don't pick up an issue already assigned to someone else. Work on the issues after it gets assigned to you.
  11. Make sure you discuss issues before working on the issue.
  12. Pull requests will be merged after being reviewed by a mentor or PA.
  13. It might take a day or two to review your pull request. Please have patience and be nice.
  14. Always create a pull request from a branch other than main.
  15. Participants / contributors have to complete issues before the decided Deadline. If you fail to make a PR within the deadline, then the issue will be assigned to another person in the queue.
  16. While making PRs, don't forget to add a description of your work.
  17. Include the issue number (Fixes:issuenumber) in your commit message while creating a pull request.
  18. Make sure your solution to any issue is better in terms of performance and other parameters in comparison to the previous work.
  19. We all are here to learn. You are allowed to make mistakes. That's how you learn, right!.

🧲Pull Requests Review Criteria

  1. You must add your script into the respective places.
  2. Your work must be original, written by you not copied from other resources.
  3. Follow the proper style guides for your work.
  4. For any queries or discussions, please feel free to join and drop a message over Discord channel.

📖Resources

  1. Markdown : Markdown is a lightweight markup language like HTML, with plain text formatting syntax.
  1. Git : Git is a distributed version-control system for tracking changes in source code during software development. It is designed for coordinating work among programmers, but it can be used to track changes in any set of files.

🤔Need more help?

You can refer to the following articles on the basics of Git and Github and also contact me, in case you are stuck: