Ray,

If you go to Settings -> Branch, you should be able to see your protected branches and who has permission to do what to them, and as project owner you should be able to change those permissions. Gitlab might have changed defaults, which would explain why you are seeing different behavior (though I would expect existing projects to stay as set). It is not unreasonable to require merge requests of everyone, even the owner. Speaking as someone who (more than once) has accidentally pushed a change to master that I intended to go to another branch, I appreciate that feature.

If that isn't the problem, then I think Erik will need to step in and investigate.

Liam

On Fri, May 19, 2017 at 10:11 AM, Raymond Toy <toy.raymond@gmail.com> wrote:

I used to be able to push commits to the master branch all the time. But in the last month or two something has changed and when I try to push a change to master, I get the message:

remote: GitLab: You are not allowed to push code to protected branches on this project.
To common-lisp.net:f2cl/f2cl.git
! [remote rejected] master -> master (pre-receive hook declined)

I see that master is a protected branch. (I don't remember changing that or if it was always protected.)

So I created a merge request Now it says I have to go find someone with write access to merge the request. Oddly, just a month ago, I successfully merged the requests https://gitlab.common-lisp.net/f2cl/f2cl/merge_requests/2 and https://gitlab.common-lisp.net/f2cl/f2cl/merge_requests/1.

As the owner, I would think I have enough rights both to push to the protected branch and to merge my own merge requests.

Any ideas?

--
Ray