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

查看:38
本文介绍了如何保护“主人"在 github 上?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我的 github 项目中有一些贡献者.我只想让他们中的一个人推动"掌握.这家伙不是我(存储库的所有者).可以吗?

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?

推荐答案

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

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:

  • 你可以使用某种提交钩子等来至少通知某人发生了错误
  • 如果你真的需要这种严格的控制,你可以使用两个存储库,一个只保存你的主"分支.然后,您需要确保只有您的家伙"才能获得对主存储库的写入权限

我认为通过一些组织来解决这个问题会更容易.在我的团队中,我们从不直接向 master 推送任何内容,而是始终创建拉取请求.这确保至少有人在代码合并之前查看一下,您还可以定义一个策略,只允许您的家伙"合并拉取请求.

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.

更新

GitHub 现在宣布他们将推出-推出了一个名为受保护分支的新功能.此功能已存在于其他 git 发行版中,例如 Atlassian Stash 多年.它将允许您保护某些分支免受推送.但是,它仍然不允许对单个分支进行完整的基于 ACL 的保护.因此,如果您不想依赖上述概述的组织解决方案,您可能需要检查此功能.

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屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆