From ecf7ebfe61f06991c45ac1a2213eed68bd5d61f8 Mon Sep 17 00:00:00 2001 From: Sergey Kanzhelev Date: Wed, 29 Jan 2025 09:25:13 -0800 Subject: [PATCH] List the best practices on configuring staging repo As discussed in https://github.com/kubernetes/test-infra/pull/34209 we want those best practices applied for all staging repositories --- contributors/devel/sig-architecture/staging.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/contributors/devel/sig-architecture/staging.md b/contributors/devel/sig-architecture/staging.md index 6ed0fb2c7..bd7523772 100644 --- a/contributors/devel/sig-architecture/staging.md +++ b/contributors/devel/sig-architecture/staging.md @@ -24,8 +24,17 @@ a published repo, the code you get is exactly the same as if you check out the It is recommend to use the semver `v0.x.y` tags for a seamless experience with go modules. +## Configuring Staging Repositories + If further repos under staging are needed, adding them to the bot is easy. Contact one of the [owners of the bot](https://git.k8s.io/publishing-bot/OWNERS). Currently, the bot is hosted on a [public CNCF cluster](https://github.com/kubernetes/publishing-bot/blob/master/production.md). + +As staging repository is not designed for direct contributions it is recommended to: + +1. Make sure README.md in the root folder explicitly stating that contributions (issues and PRs) + must be done to the Kubernetes repository, not to the staging copy. +3. Request to disable issues on the repository (like this [example](https://github.com/kubernetes/org/issues/5370)). +4. Block PRs using prow bot (like this [example](https://github.com/kubernetes/test-infra/pull/34209)).