api changes + notes #309
Closed
api changes + notes #309
Conversation
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
|
Git tip: squashing commits + force push is acceptable in all branches, except when a branch is depended on by the users ( |
graemeniedermayer
force-pushed
the
next
branch
3 times, most recently
from
9819026 to
e12909f
Compare
|
The branch with the changes is outdated. You will need to rebase it for the merge to work as expected. By the way, could you please testdrive thygate:next? I am preparing for the v0.4.3 release. |
semjon00
force-pushed
the
next
branch
5 times, most recently
from
950633e to
02e38d3
Compare
graemeniedermayer
force-pushed
the
next
branch
2 times, most recently
from
e12909f to
2d9812a
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.
This doesn't really solve api documentation at all.