This documentation contains a set of guidelines to help you during the contribution process.
We are happy to welcome all the contributions from anyone willing to improve/add new scripts to this project.
Thank you for helping out and remember, no contribution is too small.
Please note we have a code of conduct please follow it in all your interactions with the project.
You can refer to the following articles on basics of Git and Github and also contact the Project Mentors, in case you are stuck:
- Forking a Repo
- Cloning a Repo
- How to create a Pull Request
- Getting started with Git and GitHub
- Learn GitHub from Scratch
- Go to the project's issues.
- Give proper description for the issues.
- Don't spam to get the assignment of the issue 😀.
- Wait for till someone is looking into it !.
- Start working on issue only after you got assigned that issue 🚀.
Fork the repository.
Clone the forked repository on your local machine.
git clone https://github.com/<your_github_username>/EmoWell.git
Open command prompt/Terminal.
Shoot up a terminal and run:
cd EmoWell
For installing all the required dependencies and packages
npm install
This will open up the website on localhost. You can begin working. The changes will be reflected here. To access it navigate to http://localhost:5173/ in your browser
npm run dev
- Do not edit/delete someone else's script in this repository. You can only insert new files/folders into this repository.
- Give a meaningful name to whatever file or folder you are adding, changing, etc.
- Welcome to this repository, if you are here as an open-source program participant/contributor.
- Participants/contributors have to comment on issues they would like to work on, and mentors or the PA will assign you.
- Issues will be assigned on a first-come, first-serve basis.
- 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.
- When you raise an issue, make sure you get it assigned to you before you start working on that project.
- Each participant/contributor will be assigned 1 issue (max) at a time to work.
- Participants are expected to follow project guidelines and coding style . Structured code is one of our top priorities.
- Try to explain your approach to solving any issue in the comments. This will increase the chances of you being assigned.
- Don't create issues that are already listed.
- Please don't pick up an issue already assigned to someone else. Work on the issues after it gets assigned to you.
- Make sure you discuss issues before working on the issue.
- Pull requests will be merged after being reviewed by a mentor or PA.
- It might take a day or two to review your pull request. Please have patience and be nice.
- Always create a pull request from a branch other than
main. - Participants/contributors have to complete issues before they decided Deadline. If you fail to make a PR within the deadline, then the issue will be assigned to another person in the queue.
- While making PRs, don't forget to add a description of your work.
- Include the issue number (Fixes: issue number) in your commit message while creating a pull request.
- Make sure your solution to any issue is better in terms of performance and other parameters in comparison to the previous work.
- We all are here to learn. You are allowed to make mistakes. That's how you learn, right?
- Ensure that you have self reviewed your code 😀
- Make sure you have added the proper description for the functionality of the code
- I have commented my code, particularly in hard-to-understand areas.
- Add screenshot it help in review.
- Submit your PR by giving the necesarry information in PR template and hang tight we will review it really soon 🚀