Skip to content

Copy branch protections rather than renaming the pattern #26

Description

@mheap

#4 (comment)

I think you have the feature to keep the previous branch around. So maybe it should not be an update of the pattern, but a copy of the settings?

If we skip deleting the old branch (using --skip-delete-old-branch), we should copy the settings instead of updating the protection to point at our new branch

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions