From 5c3337e4936a27e5543a5c5fac58538f80792084 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Pawe=C5=82=20Wieczorek?= Date: Wed, 16 Apr 2025 10:32:18 +0200 Subject: [PATCH] docs: Avoid repetition MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit First sentence of the adjusted section already mentions ability to test the latest changes and features before they are merged into the production KernelCI API. Signed-off-by: Paweł Wieczorek --- doc/staging.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/staging.md b/doc/staging.md index 67ceb472..99d371e5 100644 --- a/doc/staging.md +++ b/doc/staging.md @@ -11,8 +11,8 @@ This environment allows you to test the latest changes and features before they merged into the production KernelCI API. If you contribute to the kernelci-core, kernelci-pipeline, or kernelci-api repositories and open a pull request, staging will automatically incorporate your changes (provided you're on the [contributor list](https://github.com/kernelci/kernelci-deploy/blob/main/data/staging.ini)) -and deploy them to the staging instance. This enables you to test your changes -and receive feedback from other contributors before merging into the production API. +and deploy them to the staging instance. This enables you to receive feedback +from other contributors before merging changes into the production API. The staging instance updates every 8 hours or can be manually triggered by the sysadmin team. You can also exclude a pull request from deployment by adding the `staging-skip` label. It is highly recommended to set such label if your pull request is not ready for