dockerfile: default linter to run on all stages by default #5000
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com>
daghack
approved these changes
Jun 6, 2024
…een progress and unmarshal test types Signed-off-by: Talon Bowler <talon.bowler@docker.com> (cherry picked from commit 6690e9a)
daghack
approved these changes
Jun 6, 2024
crazy-max
approved these changes
Jun 6, 2024
jsternberg
approved these changes
Jun 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix #4988
When linter subrequest is sent without target, the expected behavior is to check full Dockerfile, not only the last target. During build the warnings are unchanged.
Some issues with this:
ENV key valuesyntax.