Skip to content
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

hack/cherry-pick.sh: add UPSTREAM_BRANCH, apply merge commits by default #20526

Conversation

sttts
Copy link
Contributor

@sttts sttts commented Aug 2, 2018

UPSTREAM_BRANCH is needed to tell the merge commit algorithm to find the merge on the right upstream branch. This is necessary to pick from non-master branches of kube.

We now apply the merge commit (= the diff to its left parent), not single commits on the feature branch. The latter often fails because the branch point of the feature branch is often the wrong start of a commit range to apply. The merge commit instead is more stable. The old mode is available by setting APPLY_PR_COMMITS=1.

@openshift-ci-robot openshift-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Aug 2, 2018
@sttts sttts changed the title hack/cherry-pick.sh: add UPSTREAM_BRANCH AND APPLY_MERGE_COMMIT vars hack/cherry-pick.sh: add UPSTREAM_BRANCH and APPLY_MERGE_COMMIT vars Aug 2, 2018
@bparees bparees removed their request for review August 2, 2018 18:20
@sttts sttts force-pushed the sttts-cherry-pick-merge-commit-not-single-branch-commits branch from 7389420 to 9cb8cfe Compare August 2, 2018 18:52
@sttts sttts changed the title hack/cherry-pick.sh: add UPSTREAM_BRANCH and APPLY_MERGE_COMMIT vars hack/cherry-pick.sh: add UPSTREAM_BRANCH, apply merge commits by default Aug 2, 2018
@smarterclayton
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Aug 2, 2018
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: smarterclayton, sttts

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

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 2, 2018
@openshift-merge-robot openshift-merge-robot merged commit 92373ee into openshift:master Aug 2, 2018
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. lgtm 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.

None yet

4 participants