- Fork the Repository
- Start by forking the repository to your own GitHub account.
- Clone the repository
- Look for a issue you want to work on in the main repository.
- Ask the creator of that issue that you want to work on that issue
- An issue already assigned to a person can’t be assigned to you
- Any questions you have regarding that issue, you can ask in the issue’s page
- Once the issue has been assigned to you, create a new branch in your forked repository
- Branch naming guidelines:
feat/feature
- Examples
- feat/user-onboarding
- feat/login-component
- Examples
- When you are done, make a PR to the main repository
- Request the mentor for that project track as a reviewer
- Ensure your pull request has a descriptive title and includes details of your changes.
- Reference any related issues using
Fixes #issue-number
in the description.
- Branch naming guidelines:
- Your code will then be reviewed by the team, any changes required or comments will be communicated in the PR
- Maintain high-quality code by adhering to our coding standards. Ensure your code is well-documented and follows best practices.
- Write tests for your code if applicable. Ensure your changes do not break existing functionality.
- Update project documentation or README files as needed.
- Collaboration is encouraged! Feel free to ask questions, offer suggestions, and help review other contributions.
- Engage with our community and offer assistance and feedback to other contributors.