This repository was archived by the owner on Jul 18, 2025. It is now read-only.
Make email field omitempty for compatibility#115
Merged
calavera merged 1 commit intodocker-archive-public:masterfrom Feb 26, 2016
Merged
Make email field omitempty for compatibility#115calavera merged 1 commit intodocker-archive-public:masterfrom
calavera merged 1 commit intodocker-archive-public:masterfrom
Conversation
Newer instances of auth which do not include an email should not serialize the key, but existing values should not be stripped on serialization. Signed-off-by: Derek McGowan <derek@mcgstyle.net> (github: dmcgowan)
|
LGTM |
Contributor
|
LGTM 🐵 |
Contributor
|
LGTM |
calavera
added a commit
that referenced
this pull request
Feb 26, 2016
Make email field omitempty for compatibility
This was referenced Aug 22, 2025
Merged
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 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.
Newer instances of auth which do not include an email should not serialize the key,
but existing values should not be stripped on serialization.
Relevant commentary from moby/moby#20565