We should use repository rulesets to prevent the deletion or modification of released tags and critical release branches

未关闭
#14,134 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
github
领域
release, security

调研方向

首先检查 issue 中链接的仓库规则,以及 Apache Flume 的 .asf.yaml 中的标签保护示例。确认哪些已发布标签和关键发布分支需要保护,然后配置活动规则集以阻止删除和修改,同时限制绕过访问权限。完成的标准是:匹配的规则和允许的绕过角色已记录并经过验证。

由索引模型根据 Issue 内容生成。

描述

type:improvement

We can setup rules for released tags and also other branches. See our rules:

https://github.com/apache/cloudstack/rules/

Not 100% sure but seems like anyone with write access can delete releases and checkout the pictures attached

See Apache Flume they have tag protection setup in their .asf.yaml:

https://github.com/apache/logging-flume/blob/7b41e071caf1566bf73add2f40b530875d61da10/.asf.yaml#L94

Image

Yes, an Apache Software Foundation (ASF) project should use repository rulesets to prevent the deletion or modification of released tags and critical release branches.

Benefits of Using Rulesets for Releases
  • Supply Chain Security: Restricting deletions and updates on tags prevents malicious or accidental tampering with published software artifacts.
  • Flexibility and Targeting: Unlike legacy branch protection, GitHub Rulesets can target tags using naming patterns (e.g., v* or specific release tags) alongside branches.
  • Audit Transparency: Anyone with read access can view active rulesets, helping project auditors verify compliance and governance without requiring admin privileges.
  • Preventing Force Pushes: Rulesets allow projects to block force-pushes and restrict deletions to designated release managers or PMC members.
Recommended Practices
  • Set rulesets to Active enforcement for any matching patterns of released tags or stable maintenance branches.
  • Restrict bypass permissions strictly to trusted release officers or infrastructure administrators.
主要语言
Java
星标
3.1k
派生
1.4k
平均合并
6 天 20 小时
30 天内合并 PR
27

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

apache/cloudstack 的其他 Issue

查看 apache/cloudstack 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。