lenra-io / lenra-io/github-actions
[Task] Add channel generation on generate-version-names.yml
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 1
- Avg merge
- 3m
- Merged PRs (30d)
- 1
Description
What should be done
We have a a workflow that generate version all version tags for release. Useful for docker build -t $tags.
But this output for channel only one tags, we must do the same for channel version.
Technical recommendation
Any technical recommendation or specific warning about this task (if needed)
- Security issue to be warned of
- Complexity issue
- Will it scale ?
Ecological concerns
What can be done to improve the ecological impact of this task ?
- Can we minimize the data send to the network ?
- Are data stored ? Can we minimize the amount of stored data ?
- Is it CPU-intensive ? Can we reduce the CPU charge ?
- Is it RAM-intensive ? Can we reduce the RAM load ?
Is this task linked with any other ?
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 reading generate-version-names.yml and the linked pull request #27 to understand how version tags are generated. Compare the existing channel output with the version-tag output, then verify that each channel version produces the corresponding tags needed for Docker builds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100