Skip to content

CI: Allow backporting to arbitrary branch #1253

Closed

Description

@leofang

Right now, we hard-code the backport branch name here:
https://github.com/NVIDIA/cuda-python/blob/main/.github/BACKPORT_BRANCH
We should relax it and allow:

  • triggering the backport workflow manually
  • providing a branch name to overwrite the default above

Activity

  1. added this to the CI backlog milestone on Nov 17, 2025
  2. added
    P2Low priority - Nice to have
    CI/CDCI/CD infrastructure
    on Nov 17, 2025
  3. removed this from the ci backlog milestone on Apr 2, 2026
  4. rparolin commented on Aug 20, 2026

    @rparolin
    Collaborator

    Closing as done. PR #1469 added workflow_dispatch with backport-branch and pull-request inputs (backport.yml:12-21) plus the backport-to-branch job (:52-76), and it was used in production the same day — #1471 through #1476 backported to release/cuda-core-v0.5.1, a non-default branch.

    The premise is also stale: .github/BACKPORT_BRANCH, which this issue links, was deleted by #1311 in favour of ci/versions.yml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    CI/CDCI/CD infrastructureP2Low priority - Nice to have

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions