Skip to content

docs: Avoid repetition #604

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nuclearcat merged 1 commit into from
Apr 16, 2025
+2 −2
Merged

docs: Avoid repetition #604

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions doc/staging.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading