With this setting on, protection will be limited to rejecting operations requiring git push -force (rebase etc.) Since GitLab 9.3 On the same settings page you can also allow developers to push into the protected branches. You can turn on and off protection on selected branches in Project Settings (where exactly depends on GitLab version – see instructions below). master branch is protected by default – it forces developers to issue merge requests to be validated by project maintainers before integrating them into main code. By default only Maintainer/Owner users can commit to protected branches (see permissions docs). In GitLab some branches can be protected. There’s no problem – everything works as expected. Where is the problem come from? And how to fix it?Įrror: You are not allowed to push code to protected branches on this project.Įrror: failed to push some refs to … Solution I have a problem when I push my codes to git while I have developer access in my project, but everything is okay when I have master access.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |