redhat-cop / redhat-cop/openshift_virtualization_migration_ees
Configure Latest tag to use the latest version of the latest release
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
The idea is to keep all the current supported versions from 2.4 to 2.6, but the latest of the latest (in this case 2.6) will receive the latest tag on the repo:
quay.io/redhat-cop/openshift-virtualization-migration-ee:latest
For the other versions it will keep as is.
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 body is the starting reference; inspect the repository's image build and tag configuration and existing handling for versioned images. Verify that versions 2.4 through 2.6 remain available, that latest points to 2.6, and that the other version tags remain unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100