splunk / splunk/addonfactory-github-workflows

COC and CLA jobs overrides each other

未关闭
#59 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

主要语言
没有语言数据
星标
3
派生
3
PR 合并指标
30 天内没有已合并 PR

描述

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

贡献指南

这个仓库没有索引到贡献指南

从这里开始

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

调研方向

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 内容生成。

评估

技术栈
github-actions
领域
ci-cd
Issue 类型
缺陷
难度
4/5
预计耗时
3-5 天
活跃度
停滞
描述清晰度
需要澄清
新手友好度
25/100

把新 issue 发到你的邮箱

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