Skip to content

Conversation

@mohi7solanki
Copy link
Contributor

No description provided.

Copy link
Member

@ByronByron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot! It's truly appreciated.
Do you think that fixes all issues referred to by #889, so it can indeed be closed? Or would you recommend keeping the issue open as there is more/less critical issues?

@ByronByron merged commit a2d8a51 into gitpython-developers:masterSep 10, 2019
@mohi7solanki
Copy link
ContributorAuthor

@Byron I recommend creating new issues something like address deepsource issue and link to the issues page, by the way you have to create account and signup to keep analyzing on pr/push here https://deepsource.io/signup/

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@mohi7solanki@Byron