configurable container name - #11
Merged
Merged
Conversation
pinzon
self-requested a review
March 24, 2026 20:13
pinzon
approved these changes
Apr 9, 2026
pinzon
left a comment
Member
There was a problem hiding this comment.
Thanks for the improvement. I'll make a trigger a new release soon.
Member
|
Your changes are available in the latest version |
Author
|
Thank you! |
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
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.
Hi @pinzon , this change allows the container name to be set, defaulting to the existing
DEFAULT_CONTAINER_IDwhich was previously unused.