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

Forward-merge branch-23.12 into branch-24.02 #357

Closed
wants to merge 2 commits into from

Conversation

rapids-bot[bot]
Copy link

@rapids-bot rapids-bot bot commented Jul 9, 2024

Forward-merge triggered by push to branch-23.12 that creates a PR to keep branch-24.02 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.

* Update to sccache v0.7.7 (#228)

* Fix `devcontainer-utils-vault-s3-init` for `sccache@v0.7.7` (#229)

* login to dockerhub so we don't hit rate limits (#224)

* fix oneapi feature tests

* fix bad merge
* pin to rapids-dependency-file-generator<1.14
Copy link
Author

rapids-bot bot commented Jul 9, 2024

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.

@trxcllnt trxcllnt closed this Jul 9, 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.

1 participant