9elements / 9elements/firmware-action
feature request: automatic update of containers
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 22
- Forks
- 1
- Avg merge
- 10h 8m
- Merged PRs (30d)
- 9
Description
Would be nice if firmware-action could automatically update the version of containers used in projects. For example when people use ghcr.io/9elements/firmware-action/coreboot_4.19:v0.19.7, it would be nice if there was option --update-containers that would automatically update the tag, or hash.
Even check for discontinued containers would be nice. For example --check-discontinued which would fail when a discontinued container is detected.
In addition, there could be semi-automatic process of creating new containers when new tags are created in the other projects (coreboot, uboot, edk2, etc.). And automatic update for Linux kernel containers, which very often release patches.
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
The issue does not name files, tests, or existing entry points. Start by locating firmware-action's container reference handling and command-line option parsing, then clarify which update, discontinuation-check, and container-generation behaviors are in scope. Done should be defined by the agreed behavior and tests for the selected options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100