-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[NBug] Remote URLs should appear in pairs. #6577
Comments
RussKie
added a commit
to RussKie/gitextensions
that referenced
this issue
May 16, 2019
It looks like there was a change in wording after git 2.16 that changed from "fatal: Not a git..." to "fatal: not a git...". The existing parser expected the warning to be in the lower case, and thus failed for earlier versions of git. The fix makes the check case insensitive. Fixes gitextensions#6562 Closes gitextensions#6563 Closes gitextensions#6565 Closes gitextensions#6570 Closes gitextensions#6571 Closes gitextensions#6574 Closes gitextensions#6577 Closes gitextensions#6571
ghost
assigned RussKie
May 16, 2019
ghost
added
the
status: ready
label
May 16, 2019
Seeing the same on custom build, error report: Current behaviourHappening on app launch. If I just close the error popup everything continues to work as usual with no apparent problem Expected behaviourSteps to reproduceError Details
Environment
|
RussKie
added a commit
to RussKie/gitextensions
that referenced
this issue
May 17, 2019
It looks like there was a change in wording after git 2.16 that changed from "fatal: Not a git..." to "fatal: not a git...". The existing parser expected the warning to be in the lower case, and thus failed for earlier versions of git. The fix makes the check case insensitive. Fixes gitextensions#6562 Closes gitextensions#6563 Closes gitextensions#6565 Closes gitextensions#6570 Closes gitextensions#6571 Closes gitextensions#6574 Closes gitextensions#6577 Closes gitextensions#6571
Possible duplicate of #6562 |
Duplicate of #6562 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current behaviour
Expected behaviour
Steps to reproduce
Error Details
Environment
The text was updated successfully, but these errors were encountered: