Skip to content

Latest commit

 

History

History
78 lines (46 loc) · 2.49 KB

CONTRIBUTING.md

File metadata and controls

78 lines (46 loc) · 2.49 KB
Raw

Contributing Guidelines

So you have made your mind to contribute to this project? Here's everything you'll need to make your first contribution.

What can I help with?

We welcome contributions of all sorts. Even the most minor changes are warmly welcomed. You may choose to work on an existing issue or propose your own.

Some examples of contributions are:

  1. Documentation: From spell corrections to documenting the necessary information, all comes in this section.

  2. Bugs: Any bug fixes are counted in this section. If you see a new bug, feel free to create a new issue mentioning the problem faced.

  3. Design: You may like to propose some design changes for the website. If you wish to do so, create an issue mentioning the changes you want to add, like screenshots, Figma designs, or relevant information.

  4. Feature Requests: If you would like to see some new features around the website, you can always create a new issue mentioning the requested feature.

Important: Every PR must correspond to an issue. If there isn't an issue related to the PR, open a new issue in the Issues section.

Grabbing an issue

To work on an existing issue, comment on it and say you're working on that issue. Any member will assign you to the issue. This is to avoid conflicts with others also working on the issue.

You can always seek help or discuss on the issue page.

How to Contribute?

  1. Fork this repository and set up the development environment as mentioned here.

  2. Check out to a new branch for the patch.

git checkout -b <branch name>

  1. Write your code.

  2. Before committing changes, you should verify if the issue is fixed and also run the following command to format the code.

yarn format
  1. Commit your changes. Try to follow the best practices while committing changes.
git commit -s
# Then write the commit message and save changes
  1. Push the changes to your fork.
git push -u origin <branch name>

  1. Create a pull request. Be sure to read and follow our pull request guidelines!

  2. Wait for code review and address any issues raised.

  3. Voila! You made a contribution. Keep it up.

Keeping your fork up-to-date

  1. Add this repository as an upstream.
git remote add upstream https://github.com/COPS-IITBHU/hackalog-frontend.git
  1. Pull the latest changes from the main branch.
git pull upstream main