docker / docker/metadata-action
Proposal to add an input to allow fail on warnings
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.1k
- Forks
- 160
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 12
Description
Behaviour
Steps to reproduce this issue
- pass version which is a not valid semver.org version
- the action will warn you will message like
Warning: v1.5.15pre1 is not a valid semver. More info: https://semver.org/
Expected behavior
It will be nice to add some strict input to treat all warnings as errors. And if the version is invalid the docker/metadata-action step will fails
Actual behaviour
I suppose current behavior is right
This ticket just to understand if this feature is useful for someone else
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
Start by locating the action's input definitions and the warning path for invalid semver values; the issue names no files or tests. Confirm the desired strict-input behavior, then verify that invalid versions fail under strict mode while the current warning behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, typescript
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100