liquidmetal-dev / liquidmetal-dev/microvm-action-runner
should probably only run when job has `self-hosted`label?
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
noticed one time that the service was triggered even though the actual job did not use a self-hosted runner
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 by locating the service entry point that decides when to create an ad-hoc runner and review how GitHub Actions job labels are inspected. Reproduce the report with a job that does not use a self-hosted runner and compare it with one that does; done means only jobs labeled self-hosted trigger the service.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100