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

[auto-merge] bot-auto-merge-branch-24.12 to branch-25.02 [skip ci] [bot] #2750

Merged
merged 2 commits into from
Jan 10, 2025

Conversation

nvauto
Copy link
Collaborator

@nvauto nvauto commented Jan 10, 2025

auto-merge triggered by github actions on bot-auto-merge-branch-24.12 to create a PR keeping branch-25.02 up-to-date. If this PR is unable to be merged due to conflicts, it will remain open until manually fix.

nvauto and others added 2 commits January 10, 2025 10:04
Wait for the pre-merge CI job to SUCCEED

---------

Signed-off-by: nvauto <[email protected]>
Co-authored-by: YanxuanLiu <[email protected]>
Signed-off-by: spark-rapids automation <[email protected]>
@nvauto nvauto requested a review from a team as a code owner January 10, 2025 02:05
@nvauto
Copy link
Collaborator Author

nvauto commented Jan 10, 2025

FAILURE - Unable to auto-merge. Manual operation is required.

{'message': 'Pull Request is not mergeable', 'documentation_url': 'https://docs.github.com/rest/pulls/pulls#merge-a-pull-request', 'status': '405'}

Please use the following steps to fix the merge conflicts manually:

# Assume upstream is NVIDIA/spark-rapids-jni remote
git fetch upstream bot-auto-merge-branch-24.12 branch-25.02
git checkout -b fix-auto-merge-conflict-2750 upstream/branch-25.02
git merge upstream/bot-auto-merge-branch-24.12
# Fix any merge conflicts caused by this merge
git commit -am "Merge bot-auto-merge-branch-24.12 into branch-25.02"
git push <personal fork> fix-auto-merge-conflict-2750
# Open a PR targets NVIDIA/spark-rapids-jni branch-25.02

IMPORTANT: Before merging this PR, be sure to change the merging strategy to Create a merge commit (repo admin only).

Once this PR is merged, the auto-merge PR should automatically be closed since it contains the same commit hashes

@pxLi
Copy link
Collaborator

pxLi commented Jan 10, 2025

I will take care of this

@pxLi pxLi merged commit 346f192 into branch-25.02 Jan 10, 2025
2 checks passed
pxLi added a commit that referenced this pull request Jan 10, 2025
resolve conflict at #2750

this must be merged as `create a merge commit`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants