Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Figure out a plan to update release branches automatically #177

Open
Labels
help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.help-neededlifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.
@mbohlool

Description

@mbohlool

Release branches in client-python are following a release branch in kubernetes main repo. If there is a patch for main repo's branch, we should figure out a way to at least detect it, even better create a PR automatically and even much better merge that PR if it is backward compatible.

I would consider this task done if we create a PR automatically. Merging on backward compatibility would be just a plus.

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.help-neededlifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


      [8]ページ先頭

      ©2009-2025 Movatter.jp