-
Notifications
You must be signed in to change notification settings - Fork 4
Home
Rajat Talesra edited this page Aug 1, 2024
·
1 revision
Thanks for your interest in Rajat Talesra YouTube Community Learning.
You can contribute to this project as a developer.
- Fork the project and clone it to your local machine.
- Create a branch with your GitHub username and the type of the issue, for example: git checkout -b USERNAME/feature-fixing-xyz
- Code and commit your changes. Great if you write a good commit message: git commit -m 'Add some feature'
- Push to the branch: git push -u origin USERNAME/bug-fixing-xyz for your branch. 🎉
- Try to keep the pull requests small. A pull request should try its very best to address only a single concern.
- If you plan to do further work after the PR has been submitted, please use the Draft PR feature.
- Document your reasoning behind the changes. Explain why you wrote the code in the way you did. The code should explain what it does.
- If there's an existing issue related to the pull request, reference to it by adding something like References/Closes/Fixes/Resolves #305, where 305 is the issue number. More info here.
- Please fill out the PR Template when making a PR.
- Use Assignees section to request for reviews.
- Use Reviewers section to mention all the reviewers for that PR, in most cases it will be CODE_OWNERS.
- Resolve all the comments/conversations before merging the PR.
- All commits in a pull request will be squashed when merged, but when your PR is approved and passes our CI, it will eventually be live on production!
Note: Feel free to update this wiki for better and smoother collaboration.