CONTRIBUTING
Contributing to this project
First of all, thanks for taking the time to contribute! 🎉👍
Reporting Bugs
This section guides you through submitting a bug report. Following these guidelines helps maintainers and the community understand your report, reproduce the behavior, and find related reports.
Since the new GitHub Issue
forms, we only suggest you include the most information possible. But you can also Perform a cursory search to see if the report/request has already been raised. If it has, adds a comment to the existing issue instead of opening a new one.
Note: If you find a Closed issue that seems like it is the same thing that you're experiencing, open a new issue and include a link to the original issue in the body of your new one.
How Do I Submit A (Good) Bug Report? Explain the problem and include additional details to help maintainers reproduce the problem:
- Use a clear and descriptive title for the issue to identify the problem.
- Describe the exact steps which reproduce the problem in as many details as possible.
- Describe the behavior you observed after following the steps and point out what exactly is the problem with that behavior.
- Explain which behavior you expected to see instead and why.
- Include screenshots or animated GIFs which show you following the described steps and clearly demonstrate the problem. If you use the keyboard while following the steps, use this tool to record GIFs on macOS and Windows, and this tool or this tool on Linux.
Suggesting Enhancements
Feature requests are tracked as GitHub issues. Create an issue on that repository and provide the following information:
- Use a clear and descriptive title for the issue to identify the suggestion.
- Provide a in detail description of the suggested enhancement in as many details as possible.
- Explain why this enhancement would be useful to the website and the community.
Cloning the project & creating PR
Fork the repository.
Click on the fork button on the top of the page. This will create a copy of this repository in your account. Instead click here to fork the repository.
Clone the forked repository.
git clone https://github.com/<your-username>/AniLearn.dev/fork
or if use the github cli
gh repo clone <your-username>/AniLearn.dev
Navigate to the project directory.
cd AniLearn.dev
Create a new branch (naming convention: type-description-issueNo)
Kindly give your branch a more descriptive name like docs-contributing-guide-2 instead of patch-1.
You could follow this convention. Some ideas to get you started:
- Feature Updates:
- Bug Fixes:
- Documentation:
- And so on...
To create a new branch, use the following command:
git checkout -b your-branch-name
Make the necessary changes.
Stage your changes and commit.
git add . # Stages all the changes
git commit -m "<your_commit_message>"
Your commit message should be something which gives concise idea of the issue you are solving.
Push your local commits to the remote repository.
git push origin your-branch-name
Create a new pull request from your-branch-name
Congratulations! You've made your first pull request! Now, you should just wait until the maintainers review your pull request.
Know what stacks we are using here