Bump version to 0.1.1, Update Changelog #25
Merged
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
Owner
|
This is a git nit: the commit history should not look like this (it includes old commits) That's not a biggy since you can simply use the "Squash and merge" button to do the right thing, but I suggest to learn how to avoid such things in the future and have a nice intentional commits in PRs. |
vors
approved these changes
Oct 22, 2019
Owner
vors
left a comment
vors
left a comment
There was a problem hiding this comment.
LGTM, not merging because you can do it yourself! :)
Collaborator
Author
|
Thanks, @vors! Looks like I can't merge myself actually:
|
Owner
|
You need to accept the invitation to be the maintainer
Here is a link to accept: https://github.com/vors/jupyter-powershell/invitations |
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.
Bump version to 0.1.1, Update Changelog with quick description of bug fix.