如何保护“主人”在github？ [英] How to protect "master" in github?

问题描述

我的github项目中有一些贡献者。我只想让其中一个人推主。而这个人不是我（仓库的所有者）。是否可以这样做？

解决方案

当时发布这个问题时，GitHub不允许您指定访问权限在分支层面上。您只能在存储库级别执行此操作。所以你所要求的是不可能的。

如果你想解决这个限制，我个人会看到两个选择：

• 您可以使用某种提交挂钩等来至少告知某人发生了什么错误


• 如果您确实需要这种严格的控制，你可以使用两个存储库，一个只存放你的主分支。然后您需要确保只有您的家伙才能访问主存储库
这与一些组织。在我的团队中，我们从不直接向主人推送任何东西，而是始终创建拉取请求。这可以确保在代码合并之前至少有人需要查看一下，并且还可以定义一个策略，只允许您的人员合并请求。



更新





GitHub现在宣布将推出一项名为受保护分支机构的新功能。这个功能已经出现在其他git发行版中，如Atlassian Stash多年。它可以让你保护一些分支免受推挤。但是，它仍然不允许对各个分支机构进行完整的基于ACL的保护。因此，如果您不想依靠上面的概要介绍组织解决方案，则可能需要检查此功能。




I have a few contributors in my github project. I want to allow only one of them to "push" to master. And this guy is not me (the owner of the repository). Is it possible to do?

解决方案

Back then, when this question was posted, GitHub didn't allow you to specify access privileges on a branch level. You can only do it on a repository level. So what you are requesting wasn't possible.

If you want to work around this limitation, I personally see two options:

• you could use some kind of commit hooks, etc. to at least inform someone that something wrong happened
• If you really need this tight control, you could use two repositories, one only holding your "master" branch. You would then need to make sure that only your "guy" gets write access to the master repository

I think it is easier to solve that with some organisation. In my team, we never push anything directly to master, but instead always create pull requests. That ensures that at least someone takes a look before code gets merged and you could also define a policy that only your "guy" is allowed to merge pull requests.

Update

GitHub now announced that they will roll-out a new feature called protected branches. This feature has been present in other git distributions like Atlassian Stash for years. It will allow you to protect some branches from pushes. However, it still doesn't allow complete ACL-based protection of individual branches. So you might want to check this feature out in case you don't want to rely on an organizational solution as outline above.

这篇关于如何保护“主人”在github？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！