-
Suggestion
-
Resolution: Fixed
-
None
One area that I am continually wanting is some fine grained access into branch management. For instance our workflow consists of a developer creating a branch from master and pushing the topic, bug or feature branch upstream. When we go to release to each different environment we have specialty branches (develop, qa and master) which only a few people should have write access to but anyone can read.
I would like to see some finer grained permissions on who can utilize these different branches to prevent unauthorized writes. What we currently do is manage this in github and we have them issue pull requests then merge the topic branches upstream. Following that we merge them into the specialty branches since they do not have permissions to the upstream repository.
- is duplicated by
-
BSERV-2751 Branch-level permissions
- Closed
- is related to
-
BSERV-2861 Pre-receive hooks don't run when merging a pull-request
- Closed
-
BSERV-2491 Add Git Flow (branching) support
- Closed
-
BSERV-2507 Add permission to disable branch and tag deletion via git push
- Closed
-
BSERV-2521 Add commit hooks
- Closed
-
BSERV-2586 Add user permission for allowing/denying non fast forward pushes
- Closed
-
BSERV-3691 Branch Permissions per Project
- Closed
- relates to
-
BSERV-2495 Repository forking
- Closed
-
BSERV-2643 Repository Permissions
- Closed
-
BSERV-2905 Support personal branches
- Gathering Interest