liquidmetal-dev / liquidmetal-dev/microvm-action-runner
Ability to schedule runners onto hosts by tag
Open
Nobody has claimed this yet.
kind/feature
- Dominant language
- Go
- Stars
- 6
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Say someone wants to run an action on ARM, the action-runner should schedule the runner on hosts which support this.
(May require changes in flintlock)
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
No files, tests, or entry points are named. Start by tracing how the action-runner creates and selects hosts, then review the related flintlock capabilities; define the tag and ARM scheduling behavior and identify tests that demonstrate host selection before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100