Always set COMPOSE_PROJECT_NAME #628
Merged
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
ndeloof
force-pushed
the
COMPOSE_PROJECT_NAME-p
branch
from
f01b674 to
cfb8466
Compare
Signed-off-by: Nicolas De Loof <[email protected]>
ndeloof
force-pushed
the
COMPOSE_PROJECT_NAME-p
branch
from
cfb8466 to
97d7144
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.
Always set COMPOSE_PROJECT_NAME based on project name being computed from various options.
This enforce COMPOSE_PROJECT_NAME interpolation always get the expected value
fixes docker/compose#11734