Closed officeneerajsaini closed 1 month ago
Congratulations, @officeneerajsaini! 🎉 Thank you for creating your issue. Your contribution is greatly appreciated and we look forward to working with you to resolve the issue. Keep up the great work!
We will promptly review your changes and offer feedback. Keep up the excellent work! Kindly remember to check our contributing guidelines
We already have a template, but would like you @officeneerajsaini to improve it.
@SrijanShovit add level tag too.
@SrijanShovit add level tag too.
Will add once you finish working. I do remember these.
Describe the issue
Without a proper pull request (PR) template, contributors sometimes submit PRs without providing adequate descriptions of the changes they have made. This lack of information makes it challenging for reviewers to understand the purpose and scope of the changes, verify them effectively, and ensure that the code meets the project's standards. Consequently, reviewers often need to spend extra time reviewing the entire codebase, which is inefficient and time-consuming.
Steps To Reproduce
Expected Behavior
When a PR template is used:
Screenshots
Device Information [optional]
Additional Information
Implementing a PR template can significantly improve the efficiency of the code review process. A well-defined template should prompt contributors to provide:
By using a PR template, we can ensure that all necessary information is provided upfront, allowing reviewers to focus on the quality and correctness of the code rather than spending excessive time deciphering what changes have been made and why. This will not only save time for reviewers but also improve the overall quality of the codebase.