[gpuCI] Forward-merge branch-22.04 to branch-22.06 [skip gpuci]

rapidsai / clx

A collection of RAPIDS examples for security analysts, data scientists, and engineers to quickly get started applying RAPIDS and GPU acceleration to real-world cybersecurity use cases.

Apache License 2.0

168 stars 68 forks source link

[gpuCI] Forward-merge branch-22.04 to branch-22.06 [skip gpuci] #482

Closed GPUtester closed 2 years ago

GPUtester commented 2 years ago

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

GPUtester commented 2 years ago

FAILURE - Unable to forward-merge due to conflicts, manual merge is necessary. Do not use the Resolve conflicts option in this PR, follow these instructions https://docs.rapids.ai/maintainers/gpuci/#forward-mergers IMPORTANT: Before merging and approving this PR, be sure to change the merging strategy to Create a Merge Commit. Otherwise, history will be lost and the branches become incompatible.

github-actions[bot] commented 2 years ago

This PR has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this PR if it is no longer required. Otherwise, please respond with a comment indicating any updates. This PR will be labeled inactive-90d if there is no activity in the next 60 days.