Skip to content

Conversation

@nvauto
Copy link
Collaborator

@nvauto nvauto commented Feb 14, 2025

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

#838)

…ith 25.02 cuml

---------

Signed-off-by: Erik Ordentlich <[email protected]>
@nvauto
Copy link
Collaborator Author

nvauto commented Feb 14, 2025

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

{'message': 'Base branch was modified. Review and try the merge again.', '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 remote
git fetch upstream branch-25.02 branch-25.04
git checkout -b fix-auto-merge-conflict-839 upstream/branch-25.04
git merge upstream/branch-25.02
# Fix any merge conflicts caused by this merge
git commit -am "Merge branch-25.02 into branch-25.04"
git push <personal fork> fix-auto-merge-conflict-839
# Open a PR targets NVIDIA/spark-rapids branch-25.04

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 pxLi merged commit 555d95b into branch-25.04 Feb 18, 2025
11 of 12 checks passed
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.

4 participants