Sorry for not working hard on my homework. I found bunch of issues on gitlab site:
https://gitlab.com/gitlab-org/gitlab-ce/issues/15526 https://gitlab.com/gitlab-org/gitlab-ce/issues/14975 https://gitlab.com/gitlab-org/gitlab-ce/issues/18193 Look like the better way is forking at this time. On Tuesday, June 7, 2016 at 11:53:48 AM UTC-7, Benyi Wang wrote: > > If I am a master of a repository, I could push to the master branch in > gitlab directly without using a "merge request". I can always work on a > feature branch and only push there. But I still could make a mistake to put > changes into the master branch, and push them to gitlab accidentally > because changing branch is so easy in Git. > > I think it is a good practice that even masters of a repository should use > merge request to merge code into the master branch, and give team members a > chance to review your code. > > But how could you enforce this using protected branch workflow? Or the > forking workflow is the only option? > -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/5bc93ccf-a9e3-4894-9a66-a9c01a7565bb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
