From b56c80862ffc8d4873a65fe64763058b9315e1e4 Mon Sep 17 00:00:00 2001 From: "Nelo-T. Wallus" Date: Fri, 8 May 2026 18:12:50 +0200 Subject: [PATCH] Add rebase-staging to publishing rules For the rebase process we need a clean way for the changes for apimachinery and client-go to land in a branch in the staging repositories. To this end I want the branch `rebase-staging` to be published for these two. That means a maintainer can update `rebase-staging` to be up to date with main, the person rebasing PRs against this branch, the changes get reviewed, merged and published. Then the kubernetes fork can be updated targeting the `rebase-staging` branch in the respective repositories. Signed-off-by: Nelo-T. Wallus Signed-off-by: Nelo-T. Wallus --- staging/publishing/rules.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/staging/publishing/rules.yaml b/staging/publishing/rules.yaml index a93ee1bed60..07f13deeb94 100644 --- a/staging/publishing/rules.yaml +++ b/staging/publishing/rules.yaml @@ -6,6 +6,11 @@ rules: branch: main dirs: - staging/src/github.com/kcp-dev/apimachinery + - name: rebase-staging + source: + branch: rebase-staging + dirs: + - staging/src/github.com/kcp-dev/apimachinery - name: release-0.29 go: 1.24.13 source: @@ -65,6 +70,14 @@ rules: branch: main dirs: - staging/src/github.com/kcp-dev/client-go + - name: rebase-staging + dependencies: + - repository: apimachinery + branch: rebase-staging + source: + branch: rebase-staging + dirs: + - staging/src/github.com/kcp-dev/client-go - name: release-0.29 go: 1.24.13 dependencies: