Generalize SKU handling
Open
Nobody has claimed this yet.
- Dominant language
- Starlark
- Stars
- 1
- Forks
- 7
- Avg merge
- 4d 14h
- Merged PRs (30d)
- 6
Description
The build system hardcodes the selected sku using the `SKU` variable in the perso and rom_ext build files.
We should probably generalize this to all skus and see how this interacts with the github artifacts releases, which maybe should be per-sku.
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
Locate the perso and rom_ext build files and inspect how the SKU variable is hardcoded. Then trace how GitHub artifacts are produced and released; done means SKU handling is generalized and the release behavior for all SKUs is defined and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100