If you try to edit a file on a protected branch as a developer, the branch should default to patch-n

dev issue: https://dev.gitlab.org/gitlab/gitlabhq/issues/2242

If you are a developer, you are not able to commit to a protected branch.

If you still want to edit something in the UI, the branch should be set to patch-1 (if available, otherwise patch-2, etc), and you should be able to create a MR immeidately (#3059 (closed)).

cc @sytses

for having this, greying out the edit button is very confusing for our employees

Similar but different proposal: https://gitlab.com/gitlab-org/gitlab-ce/issues/3215

The workaround is to first create to create a new branch via https://gitlab.com/gitlab-com/www-gitlab-com/branches/new and then find the file and edit it.

mentioned in merge request !1820 (merged)

Reassigned to @DouweM

@DouweM awesome that you're working on this.

Working with @nearlythere today we hit the same problem when viewing the commit of a file https://gitlab.com/gitlab-org/gitlab-ce/blob/3c2914b486098c25bf94dfa14cea3d620cfed26a/.flayignore I think in this case the edit button should also lead to you patch-n

I love finding out that when I'm confused about something it might be because the UI needs a fix and not my brain. Thanks!

mentioned in merge request !2021 (merged)

Status changed to closed by commit e6668f8e

mentioned in commit e6668f8e

mentioned in merge request !2058 (merged)

Added ~122770 label

mentioned in merge request !14785