IME, to use git effectively, and make sense of the man-pages, you have to know a lot of the internals of how git works. I found it helpful to read “Git from the bottom up” when I had to start using it professionally: jwiegley.github.io/git-from-the-bottom-up/
I like SourceTree and it’s free. I don’t use it all the time, but if I’ve made a bunch of changes debugging something and I want to easily discard all of the debugging-only changes, the UI makes it really easy to commit or discard individual lines from the changeset.
Additionally, I set up an alias to open it from the command line (stree) and have it show whatever git directory I opened it from.
My experience is the opposite. A colleague who uses SourceTree and git console (for use cases not covered by SourceTree) asked me a few times to fix his branches when something went wrong (after using git console). I easily fixed it using SmartGit (paid software).
I’ve been using git for 10+ years and still sometimes do this. I know I could fix it, I also pretty much know what to do to fix it. However nuking the thing from orbit and restarting takes like 30 secs, so it’s never worth fixing.
I'm also experiencing this bug, regardless on which theme I set (Breeze, Breeze Dark, Breeze Dark EndeavourOS, Breeze Twilight). The folder icon is the only one with this problem, and only when the window has focus
Technically I can just click "Send" after it gathered some log files, but it just throws me an error. I don't remember what it was from the top of my head but I couldn't really find anything via internet search either so I just close it as that is also too much effort at this point already. Because yeah, crashes usually happen at terrible times anyway, at a point where I just can't be arsed to go through the effort to figuring out how fix it or where to even report it (the KDE bug tracker is a convoluted mess).
programming.dev
Top