[GH CI] CLA workflow gets trigerred and fails for issue comments
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 14
- Forks
- 2
- Avg merge
- 12h 42m
- Merged PRs (30d)
- 61
Description
Issue comments (not PR comments) also trigger CLA check and they fail:
example: https://github.com/vx-lang/Vx/actions/runs/35307388569/workflow
The CLA check job can be guarded with event type
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the CLA workflow and compare its behavior for issue comments versus pull request comments. Use the linked Actions run as the reproduction reference, then adjust the event guard so ordinary issue comments do not trigger the failing CLA check while pull request comments continue to be checked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100