使用GitFlow的Github保护分支

在这种情况下，我建议您不要为管理员保护分支.这样，您可以保证其他人不会直接推动开发，但是所有具有管理员访问权限的知名开发人员"都可以.不过，他们应该知道自己在做什么.您可以在https://github.com/${name}/${repo}/settings/branches/下编辑此行为.我的设置确实像这样(最后一个复选框很重要):注意:也许您也可以使用限制谁可以推送到此分支"选项.I've got a repository with my develop branch protected and I'm using the GitFlow branching model. There's two branches; develop (containing features currently being developed) and master (latest deployed production code).My develop branch prevents commits being directly made via GitHub's Protected branches. When you locally finish a hotfix using GitFlow, it automatically merges the hotfix branch into your local master and develop branches. However, pushing changes directly on the develop branch are not permitted as this is a protected branchHow can you overcome this? At the minute everytime I am creating a hotfix I have to:Manually turn off the branch protectionPush the develop branchTurn it back onThis is not automated and therefore, not really acceptable. 解决方案 Are you the owner of the GitHub project and do you have the administrator role setup with your account (or can you grant administrator access to your account)?In this case I would recommend you not to protect the branch for administrators. This way you can guarantee that other persons are not pushing directly to develop, but all "knowledged devs" with administrator access are able to. They should be aware of what they are doing, though.You can edit this behaviour under https://github.com/${name}/${repo}/settings/branches/. My settings do look like this (the last checkbox is important):Note: maybe you could also use the "Restrict who can push to this branch" option. 这篇关于使用GitFlow的Github保护分支的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！ 上岸，阿里云！