Thank you for considering contributing to this project! Your help is greatly appreciated. Below are some guidelines to follow to make the contribution process smooth and effective for everyone involved.
-
Fork the Repository:
- Navigate to the repository you want to contribute to.
- Click the "Fork" button at the top right corner of the page.
-
Clone Your Fork:
- Open your terminal and run:
git clone https://github.com/RanitManik/frontendmentor-challenges.git
- Open your terminal and run:
-
Create a Branch:
- Move into the cloned directory:
cd frontendmentor-challenges
- Create a new branch for your changes:
git checkout -b feature-branch-name
- Move into the cloned directory:
-
Make Your Changes:
- Implement your changes in your local repository.
-
Commit Your Changes:
- Add your changes:
git add .
- Commit your changes with a meaningful message:
git commit -m "Description of changes"
- Add your changes:
-
Push to Your Fork:
- Push your changes to your forked repository:
git push origin feature-branch-name
- Push your changes to your forked repository:
-
Create a Pull Request:
- Go to the original repository.
- Click the "New Pull Request" button.
- Select the branch you created and click "Create Pull Request".
- Provide a detailed description of your changes in the pull request.
- Follow the coding standards and style guides of the project.
- Write clean, readable, and maintainable code.
- Add comments where necessary to explain complex logic or decisions.
- Ensure that your changes do not break any existing functionality.
- Write tests to cover new or changed functionality if applicable.
- Run all tests to confirm that everything works as expected.
- Update the documentation if your changes include new features or modifications.
- Ensure that your documentation is clear, concise, and easy to understand.
-
Use clear and concise commit messages.
-
Follow the format:
[type]: [subject] [body] [footer]
Example:
feat: add new feature for user authentication Implemented user login and registration functionality. Added tests for the new feature. Closes #123
- If you find a bug, create an issue before submitting a pull request.
- Provide a detailed description of the bug, including steps to reproduce it.
- If possible, include screenshots or code snippets to help illustrate the issue.
- Be patient and respectful while waiting for your pull request to be reviewed.
- Address any feedback or requested changes promptly and thoughtfully.
- Engage in discussions and provide clarifications if needed.
- Follow the project's code of conduct.
- Be respectful, inclusive, and considerate in your interactions.
- Help create a welcoming and positive environment for all contributors.
We appreciate your contribution and look forward to collaborating with you!