[gpuCI] Forward-merge branch-21.10 to branch-21.12 [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-21.10 to branch-21.12 [skip gpuci] #462

Closed GPUtester closed 3 years ago

GPUtester commented 3 years ago

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