Yes, I'm sure making master no longer be a protected branch would work (but not yet tested).However, I was more concerned by that fact that as Owner, I couldn't commit to master. And why, as Owner, I couldn't even approve my own merge request to master.
I do see, now that Erik has made master no longer protected, I can now merge my merge request.--On Fri, May 19, 2017 at 11:32 AM, Erik Huelsmann <ehuels@gmail.com> wrote:Fri, May 19, 2017 at 8:30 PM, Erik Huelsmann <ehuels@gmail.com> wrote:Hi Raymond,For some reason 'master' was a protected branch. I've removed the branch protection through the project's "Settings > Repository" page. There was a "Protect branch" heading, with a listing of currently protected branches below it.For any other projects with protected branches, doing the same should be the solution.Regards,Erik.
On Fri, May 19, 2017 at 5:11 PM, 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
--
--Ray