-
Notifications
You must be signed in to change notification settings - Fork 507
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.
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
krel: Merge any commits in the remote branch before push #2128
krel: Merge any commits in the remote branch before push #2128
Conversation
To prevent divergent branches, we now fetch the remote and merge any commits found at the origin before pushing release branches. Signed-off-by: Adolfo García Veytia (Puerco) <[email protected]>
d949364
to
8096998
Compare
Testing manually for the latest 1.19 staged sources:
|
Looking good:
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: puerco, saschagrunert, xmudrii The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This commit is a revert of the following PRs: kubernetes#2128 kubernetes#2131 The reason why we are reverting this change is that merging on the main (master) branch can cause the git mainline to end up in an undesired state (i.e. it can become not straight). This can cause publishing-bot to stop working or to miss commits around the release. This issue can occur if there are merges between starting the stage and running the release step. This often happens on the master branch, especially when there's no code freeze in the effect (e.g. for alpha/beta releases). Signed-off-by: Marko Mudrinić <[email protected]>
This commit is a revert of the following PRs: kubernetes#2128 kubernetes#2131 The reason why we are reverting this change is that merging on the main (master) branch can cause the git mainline to end up in an undesired state (i.e. it can become not straight). This can cause publishing-bot to stop working or to miss commits around the release. This issue can occur if there are merges between starting the stage and running the release step. This often happens on the master branch, especially when there's no code freeze in the effect (e.g. for alpha/beta releases). Signed-off-by: Marko Mudrinić <[email protected]>
This commit is a revert of the following PRs: kubernetes#2128 kubernetes#2131 The reason why we are reverting this change is that merging on the main (master) branch can cause the git mainline to end up in an undesired state (i.e. it can become not straight). This can cause publishing-bot to stop working or to miss commits around the release. This issue can occur if there are merges between starting the stage and running the release step. This often happens on the master branch, especially when there's no code freeze in the effect (e.g. for alpha/beta releases). Signed-off-by: Marko Mudrinić <[email protected]>
What type of PR is this?
/kind feature
What this PR does / why we need it:
To prevent divergent branches, we now fetch the remote and merge any commits found at the origin before pushing release branches.
Signed-off-by: Adolfo García Veytia (Puerco) [email protected]
Which issue(s) this PR fixes:
Special notes for your reviewer:
Please take a good look at the change and if you think of a way to test it in gcb lets do it.
When running on release, krel will merge the commits from the remote branch if it finds any. It will create a merge commit. The image below is from my local test with the code of the PR in this branch:
https://github.com/puerco/lab/commits/release-1.16
The following graph shows the result. The commits at the top were made in github directly, those on the bottom on my local machine:
The code to test it:
/assign @saschagrunert @xmudrii
/priority critical-urgent
/milestone v1.22
/cc @kubernetes/release-engineering
Does this PR introduce a user-facing change?