Skip to content

Add merge commit to be picked as single commit #456

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

Merged
merged 1 commit into from
Oct 29, 2024

Conversation

akhilerm
Copy link
Member

This is done because kubernetes/kubernetes#128196 has changes split across multiple commits. One of the commits kubernetes/kubernetes@81cd728 causes a conflict with kubernetes/kubernetes@0cad1a8 while cherry-picking, which is done for linearizing history. This, however, doesn't occur while picking the merge commit as a single commit because kubernetes/kubernetes@9274a58 fixes the conflict and thus the changes are nullified across the commits in the PR. So we add the merge commit kubernetes/kubernetes@119f114 to be processed separately and picked as a single commit.

@k8s-ci-robot k8s-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 29, 2024
@k8s-ci-robot
Copy link
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Oct 29, 2024
@k8s-ci-robot k8s-ci-robot requested review from cici37 and jrsapi October 29, 2024 14:43
@k8s-ci-robot k8s-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Oct 29, 2024
@akhilerm akhilerm changed the title Pick changes from k/k@119f114 as a single commit Add merge commit to be picked as single commit Oct 29, 2024
This is done because kubernetes/kubernetes#128196 has changes split across multiple commits.
One of the commits kubernetes/kubernetes@81cd728
causes a conflict with  kubernetes/kubernetes@0cad1a8
while cherry-picking, which is done for linearizing history. This, however, doesn't occur while picking the merge commit
as a single commit because kubernetes/kubernetes@9274a58
fixes the conflict and thus the changes are nullified across the commits in the PR.
So we add the merge commit kubernetes/kubernetes@119f114 to be
processed separately and picked as a single commit.

Signed-off-by: Akhil Mohan <akhilerm@gmail.com>
@akhilerm akhilerm force-pushed the add-merge-as-single-commit branch from d533a86 to e86f0e1 Compare October 29, 2024 14:49
@akhilerm
Copy link
Member Author

/test pull-publishing-bot-test-kubernetes-master

@akhilerm akhilerm marked this pull request as ready for review October 29, 2024 16:34
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 29, 2024
@akhilerm
Copy link
Member Author

/cc @dims

@k8s-ci-robot k8s-ci-robot requested a review from dims October 29, 2024 16:34
@dims
Copy link
Member

dims commented Oct 29, 2024

/approve
/lgtm

thanks @akhilerm !!

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 29, 2024
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: akhilerm, dims

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 29, 2024
@k8s-ci-robot k8s-ci-robot merged commit bca43d5 into kubernetes:master Oct 29, 2024
8 checks passed
@akhilerm akhilerm deleted the add-merge-as-single-commit branch October 29, 2024 16:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants