rajbos / rajbos/github-actions-requests
Skip injecting the CodeQL workflow if the action is Docker based
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
If action.yaml is running a Docker image, we need to skip the CodeQL workflow since that will fail (because there is no code to be found).
Syntax:
runs:
using: docker
image: Dockerfile
Contributor guide
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 by locating the logic that injects the CodeQL workflow, then inspect action.yaml files for a runs section using Docker as shown in the issue. Done means Docker-based actions no longer receive the CodeQL workflow, while other actions continue to receive it; run the repository's available checks afterward.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100