use CustomLabels for composeV2 metadata and not impact service hash #8960
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
mat007
reviewed
Nov 24, 2021
ndeloof
force-pushed
the
custom_labels
branch
2 times, most recently
from
f0e6609
to
11d95d0
Compare
ndeloof
force-pushed
the
custom_labels
branch
from
11d95d0
to
9977e03
Compare
ndeloof
force-pushed
the
custom_labels
branch
from
9977e03
to
7d19f36
Compare
Signed-off-by: Nicolas De Loof <[email protected]>
ndeloof
force-pushed
the
custom_labels
branch
from
7d19f36
to
b3a16b7
Compare
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.
What I did
proof of concept for compose-spec/compose-go#208
Related issue
see #8725
(not mandatory) A picture of a cute animal, if possible in relation with what you did