Skip to content

Conversation

@rapids-bot
Copy link
Contributor

@rapids-bot rapids-bot bot commented Jan 30, 2026

Forward-merge triggered by push to release/26.02 that creates a PR to keep main 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 January 30, 2026 21:32
@rapids-bot rapids-bot bot requested a review from bdice January 30, 2026 21:32
@rapids-bot
Copy link
Contributor Author

rapids-bot bot commented Jan 30, 2026

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant