Skip to content

Forward-merge branch-24.04 into branch-24.06 [skip ci] - #706

Merged
raydouglass merged 1 commit into
branch-24.06from
branch-24.04
Mar 18, 2024
Merged

raydouglass merged 1 commit into
branch-24.06from
branch-24.04

Conversation

@rapids-bot

@rapids-bot rapids-bot Bot commented Mar 18, 2024

Copy link
Copy Markdown

Forward-merge triggered by push to branch-24.04 that creates a PR to keep branch-24.06 up-to-date. If this PR is unable to be immediately merged due to conflicts, it will remain open for the team to manually merge. See forward-merger docs for more info.

@rapids-bot
rapids-bot Bot requested a review from a team as a code owner March 18, 2024 18:57
@copy-pr-bot

copy-pr-bot Bot commented Mar 18, 2024

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@rapids-bot

rapids-bot Bot commented Mar 18, 2024

Copy link
Copy Markdown
Author

FAILURE - Unable to forward-merge due to an error, manual merge is necessary. Do not use the Resolve conflicts option in this PR, follow these instructions https://docs.rapids.ai/maintainers/forward-merger/

IMPORTANT: When merging this PR, do not use the auto-merger (i.e. the /merge comment). Instead, an admin must manually merge by changing the merging strategy to Create a Merge Commit. Otherwise, history will be lost and the branches become incompatible.

@raydouglass
raydouglass merged commit 71ea886 into branch-24.06 Mar 18, 2024
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