Merged
Conversation
Closed
sebest
force-pushed
the
remove-error-chain
branch
from
4f93da5 to
60a2720
Compare
Contributor
Author
|
Can we tag a new release if everything looks good? |
Contributor
Author
|
Is there anything to do to merge the PR? |
Owner
|
There's at least one other PR I'd like to try and land before I cut a new release but I plan to do it this week. Thanks for contributing! |
Owner
|
@sebest: I just cut a |
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.
All the context in is PR #44