From 2c12ede69476ca46d1dd3ccaa6c496938e37fbe6 Mon Sep 17 00:00:00 2001 From: Tuan Dang Date: Wed, 31 May 2023 12:44:30 +0300 Subject: [PATCH] Add note for prioritization of first 3 PRs for contribution due to high volume of issues, PRs, and other initiatives in the pipeline --- docs/contributing/pull-requests.mdx | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/docs/contributing/pull-requests.mdx b/docs/contributing/pull-requests.mdx index dc2d0c019..a06d9f164 100644 --- a/docs/contributing/pull-requests.mdx +++ b/docs/contributing/pull-requests.mdx @@ -37,4 +37,11 @@ Once your PR is reviewed, one or two relevent members of the Infisical team shou The team member(s) will start by enabling baseline checks to ensure that there are no leaked secrets, new dependencies are clear, and the frontend/backend services start up. Afterward, they will review your PR thoroughly by testing the code and leave any feedback or work in with you to revise the PR up to standard. -Once everything is good, the team member(s) will approve the PR to be merged into the `main` branch; all changes will be tested in CI/CD and our staging environment first before being deployed to production. \ No newline at end of file +Once everything is good, the team member(s) will approve the PR to be merged into the `main` branch; all changes will be tested in CI/CD and our staging environment first before being deployed to production. + + + Due to the high volume of issues, PRs, etc. from the community, and limited bandwidth on our end to address everything instantly, we prefer + reviewing PRs once they are fully complete and well-tested. + + In the past, we've often had to review low-quality PRs up to 10 times which severely restricts our capacity to address other issues, PRs, and initiatives in the pipeline. As such, we ask of the community to submit higher-quality PRs that, for example, don't break existing code; in return we'll prioritize the first 3 reviews for PRs. + \ No newline at end of file