Uh oh!
There was an error while loading. Please reload this page.
add a changelog entry for #1124 - #1126
Merged
Merged
Conversation
- add a changelog entry for gitpython-developers#1124 - correct duplicate entry for 3.1.12 -> 3.1.13
Byron
commented
Feb 17, 2021
Member
That's pretty much what I had in mind, and thanks again for the fly-by fix :D! When looking at these kinds of mistakes I think I probably shouldn't be steering this ship ;). |
This was referenced Mar 17, 2021
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 freeto 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.
Thanks for the kind words on #1124! This PR adds a changelog entry, although I wasn't quite sure what you wanted that to look like for a future release. I noticed there were two entries for 3.1.12, and following the links it looks like the latest should have been 3.1.13 so I fixed that while I was there.