Add rebase-staging to publishing rules#4113
Open
ntnn wants to merge 1 commit intokcp-dev:mainfrom
Open
Conversation
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 <red.brush9525@fastmail.com> Signed-off-by: Nelo-T. Wallus <n.wallus@sap.com>
kcp-ci-bot
added
do-not-merge/hold
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
kcp-ci-bot
added
the
size/S
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
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-stagingto be published for these two.That means a maintainer can update
rebase-stagingto 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-stagingbranch in the respective repositories.What Type of PR Is This?
/kind chore
/hold
Related Issue(s)
Fixes #
Release Notes