Hi @anubhav756,

The PR description used is really meant for external contributors.

As an internal contributor, we should be getting in the habit of writing pull request descriptions that give a quick summary of the feature/fix. This helps reviewers by giving them context prior to reviewing the code changes and helps conform to open-source best practices, improves changelogs etc.

Github themselves recommends this in their pull request best practices:

Write clear titles and descriptions for your pull requests so that reviewers can quickly understand what the pull request does. In the pull request body, include:

• the purpose of the pull request
• an overview of what changed
• links to any additional context such as tracking issues or previous conversations

Let me know if you have any questions, happy to show some examples if need be 😄

Hi @anubhav756,

The PR description used is really meant for external contributors.

As an internal contributor, we should be getting in the habit of writing pull request descriptions that give a quick summary of the feature/fix. This helps reviewers by giving them context prior to reviewing the code changes and helps conform to open-source best practices, improves changelogs etc.

Github themselves recommends this in their pull request best practices:

Write clear titles and descriptions for your pull requests so that reviewers can quickly understand what the pull request does. In the pull request body, include:

• the purpose of the pull request
• an overview of what changed
• links to any additional context such as tracking issues or previous conversations

Let me know if you have any questions, happy to show some examples if need be 😄

Thanks for the suggestion Jack. This is a great recommendation. I will definitely keep this in mind going forward 🙂