Thank you for investing your time in contributing to our project! Any contribution you make will be reflected on campUS-Website 🎇✨
Read our Code of Conduct to keep our community approachable and respectable.
In this guide, you will get an overview of the contribution workflow from opening an issue, creating a PR, reviewing, and merging the PR.
To get an overview of the project, read the README. Here are some resources to help you get started with open-source contributions:
- Finding ways to contribute to open source on GitHub
- Set up Git
- GitHub flow
- Collaborating with pull requests
Scan through our existing issues to find one that interests you. You can narrow down the search using labels as filters. As a general rule, we don’t assign issues to anyone. If you find an issue to work on, you are welcome to open a PR with a fix.
When you are ready to start working on an issue, you can open a pull request (PR) in the repository. PRs are the heart of collaboration on GitHub. When you open a PR, you’re proposing your changes and requesting that someone review and pull in your contribution and merge them into their branch. Pull requests show diffs, or differences, of the content from both branches. The changes, additions, and subtractions are shown in green and red. Maintianer will review your PR and if it meets the requirements, it will be merged.
Congratulations 🎉🎉 The GDSC JSSSTU team thanks you ✨✨
Once your PR is merged, your contributions will be publicly visible on the HDU-Website
Now that you are part of the GDSC JSSSTU community, see how else you can contribute to the community reopsitories
If you want to ask a question, we assume that you have read the available Documentation.
Before you ask a question, it is best to search for existing Issues that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
If you then still feel the need to ask a question and need clarification, we recommend the following:
- Open an Issue.
- Provide as much context as you can about what you're running into.
- Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant.
We will then take care of the issue as soon as possible.
When contributing to this project, you must agree that you have authored 100% of the content, that you have the necessary rights to the content and that the content you contribute may be provided under the project licence.