Tagging Docker images as "latest" isn't working (v0.0.15)
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 1
- Avg merge
- 17h 48m
- Merged PRs (30d)
- 1
Description
Story
I recently merged a PR into the main branch in scientist-softserv/atla-hyku using Actions v0.0.15. The Docker image successfully built and pushed to the registry, but it didn't have the latest tag; that was still on a previous build that ran with v0.0.14 of the action.
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
Compare the linked v0.0.14 and v0.0.15 workflow runs and inspect the action behavior responsible for Docker image tags. Reproduce the main-branch build if possible; done means the pushed image receives the latest tag instead of leaving it on the previous build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100