Bash? On Windows? about lazygit HOT 9 CLOSED

I just pushed 7e5d7bf which should fix the first issue (please let me know if it doesn't)

As for the second issue, There is currently a PR open that once merged will let us interact with the git prompt, but currently that isn't an option. In the meantime, if you are receiving this prompt each time you pull/push from a particular repo and you trust this repo, you may want to look into some of these stack overflow answers (note there are security considerations to take however) https://stackoverflow.com/questions/3663895/ssh-the-authenticity-of-host-hostname-cant-be-established

from lazygit.

Now there's a different error.

from lazygit.

That's git telling you that it doesn't know how to show the graph of the branch, because you have no tracking information on it. If you pull (press 'p') that error should go away. I'll make a note to hide that error if it appears because it's not very user-friendly

from lazygit.

Ok this is just funny now. After pressing p...

from lazygit.

hmm that's strange. If you didn't edit those files, and I assume you didn't, then they shouldn't be showing up there. You can get around that by doing git reset --hard head on the command line.

For diagnostic purposes, if you do a git status on the command line, does it say that you're on the master branch? I think there could be an issue with the application not showing the master branch for windows users

from lazygit.

The repo I'm using is the lazygit repo, and all the text files have changed from LF to CRLF. (EDIT: Actually, I'm just guessing that's whats changed, as I don't know what line ending is in the repo.)

Git status says the working tree is clean, on master branch, so I suspect there is an issue with the display on windows.

from lazygit.

I just fixed this in 694b192, hopefully that resolves the issue about lazygit thinking you're on the wrong branch.

As for the CRLF's, this may be a bit trickier to solve. I need to catch up on some sleep but I'll have another look into that tomorrow. If anybody is reading and knows a bit about CRLF's and how to deal with them in git, please do chip in!

from lazygit.

I've got a catch-all PR intended to resolve any issues on windows, #53. Please let me know if your issues still persist after checking this out

from lazygit.

Closing due to inactivity

from lazygit.