diff --git a/llvm/docs/CodeReview.rst b/llvm/docs/CodeReview.rst index f1d5b6c9c9920..e3a74946e5933 100644 --- a/llvm/docs/CodeReview.rst +++ b/llvm/docs/CodeReview.rst @@ -103,6 +103,12 @@ ready to be committed. Specifically, once a patch is sent out for review, it needs an explicit approval before it is committed. Do not assume silent approval, or solicit objections to a patch with a deadline. +.. note:: + If you are using a Pull Request for purposes other than review + (eg: precommit CI results, convenient web-based reverts, etc) + `skip-precommit-approval` + label to the PR. + Acknowledge All Reviewer Feedback --------------------------------- diff --git a/llvm/docs/GitHub.rst b/llvm/docs/GitHub.rst index c3fbb64c2dd96..51a7310a8a72d 100644 --- a/llvm/docs/GitHub.rst +++ b/llvm/docs/GitHub.rst @@ -30,6 +30,12 @@ describes the typical workflow of creating a Pull Request and getting it reviewe and accepted. This is meant as an overview of the GitHub workflow, for complete documentation refer to `GitHub's documentation `_. +.. note:: + If you are using a Pull Request for purposes other than review + (eg: precommit CI results, convenient web-based reverts, etc) + `skip-precommit-approval` + label to the PR. + GitHub Tools ------------ You can interact with GitHub in several ways: via git command line tools,