如何防止个人或团队编辑特定存储库的基于GitHub操作的工作流程?
我有一个具有基于GITHUB操作的工作流程的GIHUB存储库(/。github/workflows/build.yml
)来进行CI构建。
我来自DevOps团队,我的案例,开发团队的人们不允许更改CI管道,他们可以在功能分支上更改所需的任何内容,除了/。github/workflows/build.yml.yml
。
如何防止开发人员更改Githib工作流程以查看他的应用程序通过不同类型的集成构建质量检查的更改?
除了下面提到的选项外,是否有更好的方法可以实现这一目标?
1] Through PR reviews
2] Script/automation to validate PR to see if dev did any changes to (/.github/workflows/build.yml)
I have a GiHub repository with GitHub actions based workflow (/.github/workflows/build.yml
) to do CI builds.
I am from the DevOps team, my case, folks from development team are not allowed to change CI pipelines, they can change whatever they want on a feature branch except /.github/workflows/build.yml
.
How to prevent a developer changing GitHib workflow to see his app changes passing through different type of integration build quality checks?
Is there any better approach to achieve this other than options mentioned below?
1] Through PR reviews
2] Script/automation to validate PR to see if dev did any changes to (/.github/workflows/build.yml)
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
使用代码所有者您可以指定允许谁修改某些文件这样的文件:
有点偏离主题,但请注意,不建议您分离代码和管道所有权:
With code owners you can specify who is allowed to modify certain files like so:
Somewhat off-topic, but note that Toughtworks does not recommend to separate code and pipeline ownership: