Skip to content

Latest commit

 

History

History
51 lines (31 loc) · 2.7 KB

CONTRIBUTING.md

File metadata and controls

51 lines (31 loc) · 2.7 KB

learnJava contributing guidelines

Thank you for taking the time to contribute to our project! Please take a moment to read the following guidelines before contributing:

⚠️IMPORTANT Note

Pull Requests having no issue associated with them will not be accepted. Firstly get an issue assigned, whether it's already opened or raised by you, and then create a Pull Request.

Prerequisites

  • Open Source Etiquette: If you've never contributed to an open source project before, have a read of Basic etiquette for open source projects.

  • Basic familiarity with Git and GitHub: If you are also new to these tools, visit GitHub for complete beginners for a comprehensive introduction to them

How to Contribute 🤔

Look at the existing Issues or create a new issue!

  • Fork the Repo. Then, create a branch for any issue that you are working on. Finally, commit your work.
  • Create a Pull Request (PR), which will be promptly reviewed and given suggestions for improvements by the community.
  • Add screenshots or screen captures to your Pull Request to help us understand the effects of the changes proposed in your PR.

Adding new Links 🔗

✨ You can also create issue(s) for inserting your links and someone else will take care of them.

🌟Follow these steps to get your Content/Code added into the Repository

  • A newly created category and subcategory should be added to the data file

  • Each category has it's own folder with it's name

  • Every subcategory should be placed in it respective category folder

    i.e images should be inside Frontend folder

  • To add a new category ensure to create a folder with it's name

    i.e Resources

NOTE When you're adding a YouTube channel's link, please specify language of the channel they are using to teach in for example English, Hindi, Spanish etc. If the language is NOT specified, remove the language property.

⚠️Important

  • Do not make duplicate entries.
  • Ensure that your entries are error-free by double-checking before staging your changes.
  • Your entries should follow the above structure.

Remarks ✅

If something is missing here, or you feel something is not well described, either directly create a PR or create an issue.