Support For Granular Locking Mechanisms.
未关闭
question
- 主要语言
- TypeScript
- 星标
- 576
- 派生
- 74
- 平均合并
- 11 小时 7 分钟
- 30 天内合并 PR
- 1
描述
### Details
First of all, we really thank you for this project. It's really one of my favorite GHA related projects.
## The Problem
We recently realized that sticky locks lock on a user level, not on a PR level.
This recently caused a problem for us because one of our developers forgot to merge and deployed another PR, effectively rolling back the changes of his previous PR.
## The Suggestion
We would like it if locks could also work on a PR or Branch basis.
---
I would be glad to contribute if that's ok, but I wanted to check if my assumption and suggestion was valid first.
贡献指南
调研方向
没有指定文件、测试或入口点。先定位现有的 sticky-lock 处理逻辑和部署工作流,然后明确锁的作用域应限定为 pull request、分支,还是两者都包括。Done 应包括已达成一致的细粒度行为,以及对相关加锁场景的覆盖。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- github-actions, typescript
- 领域
- ci-cd, devops
- Issue 类型
- 功能
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100