Branches and Protected branches pages should be a single page
/:group/:project/protected_branches and /:group/:project/branches should be in a single page, rather than over two seperate pages. You simply set the protection where it is needed.
@creamzy @skyruler could you work on a way to do this? Let me know if you have any questions.
I chose the milestone semi-randomly, is flexible.
Activity
@JobV on it, can you give more info as it's more about info to be displayed? My feeling is protected page is more recent. Also do you think we need to show Protected sign inside the page?
Reassigned to @skyruler
Reassigned to @JobV
My feeling is protected page is more recent.
Correct.
Also do you think we need to show Protected sign inside the page?
Yes.
We want to:
- show all branches (searchable)
- show which are protected
- have the ability to protect or unprotect a branch
- have the ability to allow developers to push IF the branch is protected (as you can see on the protected branches page)
There should also be some way to transmit to the inexperienced user what a protected branch is. This used to be obscure, but is not getting more and more known.
Milestone changed to 8.5
- Edited by username-removed-127938
Reassigned to @skyruler
@skyruler love it.
Added frontend label
Milestone changed to 8.6
Milestone changed to 8.7
Hi team, I think it would be a good idea if we could multi-select (or wildcard select) branches to change to protected. Ex: Protect all branches release/*
Edited by username-removed-294477Milestone changed to 8.8
Reassigned to @iamphill
mentioned in merge request !4179 (closed)
Milestone changed to %8.9
Removed frontend repository labels
Milestone changed to %8.10
mentioned in issue #19034 (closed)
mentioned in issue #17982 (closed)
!4179 (closed) is still open and also covered #18678 (closed) which we should do separately then.
mentioned in merge request !5462 (merged)
mentioned in issue #26223 (moved)
mentioned in merge request !14785
