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] branch-22.06 to branch-22.08 [skip ci] [bot] #5699

Closed
wants to merge 2 commits into from

Conversation

nvauto
Copy link
Collaborator

@nvauto nvauto commented May 31, 2022

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

Temporarily allow 3.3.1 while 3.3.0 release candidates are being produced

Signed-off-by: Firestarman <firestarmanllc@gmail.com>
@nvauto
Copy link
Collaborator Author

nvauto commented May 31, 2022

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

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

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

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

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

@tgravescs
Copy link
Collaborator

#5700

* init

Signed-off-by: sperlingxx <lovedreamf@gmail.com>

* shuffled test columns

Signed-off-by: sperlingxx <lovedreamf@gmail.com>
@tgravescs tgravescs closed this May 31, 2022
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