feat: ensure Dockerfiles being up-to-date #162
Conversation
This file contains hidden or 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
develop7
force-pushed
the
push-lnzuuwkzwukz
branch
11 times, most recently
from
761e5f6 to
92d7a5c
Compare
develop7
force-pushed
the
push-lnzuuwkzwukz
branch
4 times, most recently
from
8cce804 to
f575b9a
Compare
|
Awesome! I'm curious, why do you pull the generator binary from a different workflow, rather than just use |
develop7
force-pushed
the
push-lnzuuwkzwukz
branch
from
f575b9a to
ada5de4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Introduces linting workflow that makes sure generated Dockerfiles are up-to-date