Skip to content

[submodule-sync] bot-submodule-sync-release/26.04 to release/26.04 [skip ci] [bot]#4384

Merged
nvauto merged 1 commit intorelease/26.04from
bot-submodule-sync-release/26.04
Mar 17, 2026
Merged

[submodule-sync] bot-submodule-sync-release/26.04 to release/26.04 [skip ci] [bot]#4384
nvauto merged 1 commit intorelease/26.04from
bot-submodule-sync-release/26.04

Conversation

@nvauto
Copy link
Copy Markdown
Collaborator

@nvauto nvauto commented Mar 17, 2026

submodule-sync to create a PR keeping thirdparty/cudf up-to-date.
HEAD commit SHA: d18fffd, cudf commit SHA: rapidsai/cudf@b13ada2

This PR will be auto-merged if test passed. If failed, it will remain open until test pass or manually fix.

Signed-off-by: spark-rapids automation <70000568+nvauto@users.noreply.github.com>
@nvauto
Copy link
Copy Markdown
Collaborator Author

nvauto commented Mar 17, 2026

HEAD commit SHA: d18fffd, CUDF commit SHA: rapidsai/cudf@b13ada2
Test passed: True

@nvauto nvauto merged commit 56318d9 into release/26.04 Mar 17, 2026
@nvauto
Copy link
Copy Markdown
Collaborator Author

nvauto commented Mar 17, 2026

SUCCESS - auto-merge

@nvauto nvauto deleted the bot-submodule-sync-release/26.04 branch March 17, 2026 07:55
@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps bot commented Mar 17, 2026

Greptile Summary

This is an automated bot PR that advances the thirdparty/cudf git submodule pointer from 0f291eb1c9be371300468349b0621c23a578fccd to b13ada2c8970be62e713d197e0ad3fa596ea32ef on the release/26.04 branch.

  • Only change is a single submodule reference update in thirdparty/cudf — no source code, build scripts, or configuration files were modified.
  • The PR is tagged [skip ci] by the bot but includes a note that it will auto-merge once tests pass, which is the standard workflow for submodule-sync PRs in this repository.
  • No logic, syntax, or style issues were identified.

Confidence Score: 5/5

  • This PR is safe to merge — it is a routine automated submodule pointer bump with no code changes.
  • The entire change is a one-line submodule SHA update generated by the nvauto bot. There are no source-code modifications, no configuration changes, and no logic to review. Risk is limited to whatever changes exist in the new cudf commit, which is managed upstream.
  • No files require special attention.

Important Files Changed

Filename Overview
thirdparty/cudf Submodule pointer updated from 0f291eb1c9be371300468349b0621c23a578fccd to b13ada2c8970be62e713d197e0ad3fa596ea32ef; automated bot change with no logical issues.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[nvauto bot detects cudf upstream update] --> B[Creates submodule-sync PR on release/26.04]
    B --> C{CI tests pass?}
    C -- Yes --> D[Auto-merge PR]
    C -- No --> E[PR stays open for manual fix]
    D --> F[thirdparty/cudf pointer updated\n0f291eb → b13ada2]
Loading

Last reviewed commit: d18fffd

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.

1 participant