Removed self-hosted YAML Serializer and PsychedYAML#3396
Closed
hsbt wants to merge 1 commit into
Closed
Conversation
hsbt
changed the title
simi
force-pushed
the
remove-self-hosted-yaml
branch
from
ff79d78 to
65f4ce1
Compare
|
@hsbt I have rebased this (also to restart CI since old logs were not available anymore). I hope that is fine. Would it be possible to remove |
simi
force-pushed
the
remove-self-hosted-yaml
branch
from
65f4ce1 to
ef5c627
Compare
Member
Author
|
I gave up to migrate self-hosted YAML serializer to |
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
3 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.
Description:
Migrate from rubygems/bundler#6536
I hope to unify the specification of YAML serializer in Rubygems. But We have a some of the activated issues related to the default gems.
Tasks:
I will abide by the code of conduct.