fe7fcdb227
Reviewed By: mkonicek Differential Revision:D3054017 Ninja: oss only fb-gh-sync-id: df545cb45ae8de3f56f671b06cab84b1f947a01c shipit-source-id: df545cb45ae8de3f56f671b06cab84b1f947a01c
1.1 KiB
Tips on reviewing pull requests
Does the PR miss info required in the Pull request template? Ask for it and link to the template. Add labels 'Needs revision' and 'Needs response from author'. Examples: #6395. Example:
Hey @author, thanks for sending the pull request. Can you please add all the info specified in the template? This is necessary for people to be able to understand and review your pull request.
Does the code style match the Style guide, especially consistency with the rest of the codebase? If not, link to the style guide and add the label 'Needs revision'.
Does the pull request add a completely new feature we don't want to add to the core and maintain? Ask the author to release it a separate npm module.
Does the pull request do several unrelated things at the same time? Ask the author to split it.