Hello dears;
Members with edit permission level can not create new branch any more. Please advise
Hi! jam_zaw Thanks for your feedback.We understand that the recent changes to our permission system, which were part of a broader overhaul, have affected your user permissions in ways we didn’t anticipate. Our product team is looking into this and working with the product manager to find a solution. We’re sorry for any inconvenience this has caused. Right now, only admins can create branches. I’ll be in touch if we make any progress. Thanks again for your patience.
Hello, currently, members with edit permissions cannot create new branches.
This change is due to our recent implementation of branch protection, which requires modifications to protected branches to be submitted via merge requests and reviewed. Allowing editors to create branches freely might lead to unreviewed changes being merged into protected branches. So we suggest that admins create branches to better control the content of the branches and prevent unexpected changes.
If this design causes any inconvenience, please let us know and we will work on optimizing it.
This design is totally not practical nor correct. Now we need to make everyone in the team admin so they can manage and work!
It doesn’t make sense to ask a member in a team to create a branch, then to ask another member to design the endpoints!
This implementation stopped us during the last days and no one is working now.
Besides, users with editor access now, can’t edit and save existing endpoints!
This bug is really blocking us now.
Ok, if it’s blocking your work, we can open the permission to create branches for editors ASAP.
“Besides, users with editor access now, can’t edit and save existing endpoints!” --we have not yet reproduced this issue. Are you referring to branches that have been set as protected, which editors cannot edit? If so, removing branch protection should solve the problem. You can check here for more info: Manage sprint branches - Apidog Docs
Great thanks Joe that would be appreciated.
For the saving issue, it’s happening in an unprotected branch. I will send you details later today.
Joe any update please?
Currently, we have quickly optimized the ability for editor to create new sprint branches, which should take effect after a refresh.
Meanwhile, we have overall optimized the permissions here, allowing editor to directly merge into non-protected branches by default and create merge requests for protected branches. This optimization is expected to be released next week.
Hello, currently, members with edit permissions cannot create new branches.
This change is due to our recent implementation of branch protection, which requires modifications to protected branches to be submitted via merge requests and reviewed. Allowing editors to create branches freely might lead to unreviewed changes being merged into protected branches. So we suggest that admins create branches to better control the content of the branches and prevent unexpected changes.
If this design causes any inconvenience, please let us know and we will work on optimizing it.
This bug is really blocking us now.
Ok, if it’s blocking your work, we can open the permission to create branches for editors ASAP.
“Besides, users with editor access now, can’t edit and save existing endpoints!” --we have not yet reproduced this issue. Are you referring to branches that have been set as protected, which editors cannot edit? If so, removing branch protection should solve the problem. You can check here for more info: Manage sprint branches - Apidog Docs
Joe any update please?
Currently, we have quickly optimized the ability for editor to create new sprint branches, which should take effect after a refresh.
Meanwhile, we have overall optimized the permissions here, allowing editor to directly merge into non-protected branches by default and create merge requests for protected branches. This optimization is expected to be released next week.