From f32884d9b819e5680df1ed80531ae0c076d5bd48 Mon Sep 17 00:00:00 2001 From: Emile Vauge Date: Wed, 10 Jul 2024 11:46:03 +0200 Subject: [PATCH] Update PR approval process --- docs/content/contributing/submitting-pull-requests.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/content/contributing/submitting-pull-requests.md b/docs/content/contributing/submitting-pull-requests.md index 8dfbaeb5c..c5d76f6f1 100644 --- a/docs/content/contributing/submitting-pull-requests.md +++ b/docs/content/contributing/submitting-pull-requests.md @@ -56,7 +56,7 @@ Merging a PR requires the following steps to be completed before it is merged au * Ensure your PR is not a draft. We do not review drafts, but do answer questions and confer with developers on them as needed. * Pass the validation check. * Pass all tests. -* Receive 3 approving reviews from maintainers. +* Receive 2 approving reviews from maintainers. ## Pull Request Review Cycle @@ -112,7 +112,7 @@ In such a situation, solve the conflicts/CI/... and then remove the label `bot/n To prevent the bot from automatically merging a PR, add the label `bot/no-merge`. -The label `bot/light-review` decreases the number of required LGTM from 3 to 1. +The label `bot/light-review` decreases the number of required LGTM from 2 to 1. This label can be used when: