Skip to content

Additional branch.protect() fields #821

Closed

Description

@plantusd

Description of the problem, including code/CLI snippet

image

Expected Behavior

Can you also add
maintainers_can_push=, maintainers_can_merge=

Activity

  1. max-wittig commented on Jul 10, 2019

    @max-wittig
    Member

    Have you tried it. Should work as it's send to the GitLab API.

  2. plantusd commented on Jul 10, 2019

    @plantusd
    Author

    Yes, here
    image

    image

    Thanks in advance!

  3. max-wittig commented on Jul 10, 2019

    @max-wittig
    Member

    lazy doesn't help you here.

    The syntax is different. See examples here: https://python-gitlab.readthedocs.io/en/stable/gl_objects/protected_branches.html#examples

  4. max-wittig commented on Jul 10, 2019

    @max-wittig
    Member

    You need to create a protected branch, after creating a normal branch

  5. plantusd commented on Jul 10, 2019

    @plantusd
    Author

    yes, i get it, but whats the point to make branch.protect() with
    developers_can_push=,
    developers_can_merge=

    w/o

    maintainers_can_push=,
    maintainers_can_merge=

    or i just simply don't get it

  6. locked as resolved and limited conversation to collaborators on Oct 10, 2022
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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions