CI: Automate backport process more

Open
#965 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions
Domain
ci-cd, tooling

Research direction

Start by inspecting the backport bot configuration under .github/ and the handling of cuda.bindings regeneration. Determine how the bot currently handles permission failures and generated files; done means backports work for .github/ changes and for changes requiring cuda.bindings regeneration.

Written by the indexing model from the issue text.

Description

CI/CD cuda.bindings enhancement

We have a backport bot but it does not always work:

  • Any PR touching files under .github/ cannot be backported by the bot due to permission issues
  • cuda.bindings most of the time needs to be regenerated, so a naive backport does not always work either
Dominant language
Cython
Stars
3.4k
Forks
329
Avg merge
1d 21h
Merged PRs (30d)
113

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NVIDIA/cuda-python

All issues in NVIDIA/cuda-python

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.