COC and CLA jobs overrides each other
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 25/100
- Issue 类型
- 缺陷
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- github-actions
- 领域
- ci-cd
调研方向
Start by reviewing the reusable workflow definitions in this repository and contributor-assistant/github-action's src/pullrequest/pullRequestComment.ts around line 58. Reproduce the CLA and COC jobs running together, then determine which workflow-level or action-level approach preserves both messages. Done means the two checks no longer overwrite each other's user-facing comments.
由索引模型根据 Issue 内容生成。
描述
The issue
The first job asks about CLA, then another job, COC, runs and overrides the comment from the first one. The end user sees the latest message about COC and has no idea of that CLA also has to be signed.
It seems like a bug (or feature) of contributor-assistant/github-action:
https://github.com/contributor-assistant/github-action/blob/master/src/pullrequest/pullRequestComment.ts#L58
It looks for the first occurance of comment with CLA Assistant Lite bot and edits that comment. This github action is not supposed to work as jobs simultaneously.
Solutions
Possible solution 1: merge CLA and COC into a single job.
Possible solution 2: find another alternative for contributor-assistant/github-action
- 主要语言
- 没有语言数据
- 星标
- 3
- 派生
- 3
- 平均合并
- 9 天 23 小时
- 30 天内合并 PR
- 1
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
相似的 Issue
-
area:ci bug triage:confirmed
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
ready-for-triage
难度 1/5 1 小时以内 新手友好度 88/100
konflux-ci/konflux-ui#1596 · 1 条评论 ·
维护者通常 1 天内回复
-
[Bug]: core doesn't build standalone on dev since a17068054 (go-mp3 require dropped, go.sum pruned)未关闭
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
priority: P3 type: devops
难度 2/5 1-3 小时 新手友好度 75/100
jiegui2025/hwspec#57 ·
维护者通常 1 天内回复
-
area: release bug
难度 2/5 1-3 小时 新手友好度 78/100
TMHSDigital/subenum#102 ·
维护者通常 1 天内回复