Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The lazy Git UI you didn't know you need

bwplotka.dev

Post reply on HN
Print view View original

161–170 of 224 posts

Re: The lazy Git UI you didn't know you need

#161

Post by scotty79 »

jeroenhd wrote: post #120
scotty79 wrote: post #107

After years of using git I got back to svn. Svn has one great feature, you can checkout (clone) repo partially. This way I can keep all my experiments in a single remote repo and easily pull any part of any project locally wherever I want. I don't really care about branching in svn. If I want to try variants of some code I still use git with multiple branches. I'm not sure what I would prefer for a team project. I'm…

> I'm sure svn got decent merging. That's definitely not my experience. SVN has merging, but I've found it extremely frustrating in a team context.

When did you experience it last time? I remember it being bad, but it was before git was created.

Re: The lazy Git UI you didn't know you need

#162

Post by xaedes »

damethos wrote: post #118
prmph wrote: post #7

You might laugh, but in years of serious development, I have not come across a better git UI tool than SourceTree. If I want to be hard-core, I'd use the original git CLI. SourceTree is unmatched in how it makes using git so much more pleasant for when you need to do something relatively simple, but which would be quite cumbersome to do with the CLI and most other tools I've tried. Its file status and history view is…

I was using SmartGit for many years and was very happy with it, until they made it subscription based and had to switch to SourceTree. It works but I do not find it very smooth at all. It hangs every now (using MacOSX) and in general the experience is not as smooth as it was with SmartGit. I am surprised that you are saying that you haven't come across any better tool.

For a few minutes after reading this I was worried about smartgit losing its way. But it seems they actually still offer perpetual single-payment licenses, where you purchase a few years of updates, usable after update period ends.

Re: The lazy Git UI you didn't know you need

#163

Post by TiredOfLife »

9dev wrote: post #25
prmph wrote: post #7

You might laugh, but in years of serious development, I have not come across a better git UI tool than SourceTree. If I want to be hard-core, I'd use the original git CLI. SourceTree is unmatched in how it makes using git so much more pleasant for when you need to do something relatively simple, but which would be quite cumbersome to do with the CLI and most other tools I've tried. Its file status and history view is…

Have you tried the Jetbrains IDE git client yet? It hits the perfect spot for me.

Unfortunately the standalone one was cancelled

Re: The lazy Git UI you didn't know you need

#164

Post by icorbrey »

greenicon wrote: post #160
__float wrote: post #105

Earlier quoted context omitted.

I try to leave a good commit trail in my PRs. These are often _not_ the reality of how the code was written and originally committed, but a rough approximation of the intended steps with the benefit of hindsight. A tool like https://github.com/tummychow/git-absorb has been on my to-try list for a while, but for now I do it by hand.

git absorb works surprisingly well. I was quite skeptical in the beginning, but it really turned into something I used daily (until I switched to jj, where I haven't found a replacement yet). If you use stepwise commits I can really recommend it. small edit: It seems that jj supports `jj absorb` now as well. Wonderful!

Indeed, though I don't think it can create fixup commits if that's what you're looking for. However, it might work great for that if you pair it with jj-spr: https://github.com/LucioFranco/jj-spr

Re: The lazy Git UI you didn't know you need

#165

Post by icorbrey »

stavros wrote: post #150
MrGreenTea wrote: post #137

Earlier quoted context omitted.

The compatibility with git is the whole reason it's so popular (just run `jj git init --colocate` in your git repo). You can use it without forcing your collaborators to switch from git and you can use it will a git forges as well.

I don't think you need `--colocate` any more, and maybe you don't even need `git`? I tried `jj init` in a git repo the other day and it did create a colocated jj repo, as far as I could see.

Not sure on `jj init`, but yeah colocation is default as of I believe 0.34

Re: The lazy Git UI you didn't know you need

#166

Post by dgritsko »

prmph wrote: post #7

You might laugh, but in years of serious development, I have not come across a better git UI tool than SourceTree. If I want to be hard-core, I'd use the original git CLI. SourceTree is unmatched in how it makes using git so much more pleasant for when you need to do something relatively simple, but which would be quite cumbersome to do with the CLI and most other tools I've tried. Its file status and history view is…

Fellow SourceTree apologist here. It remains one of the first things I install on a new machine. I'll do simple stuff directly in the CLI, but stick with SourceTree for anything moderately complicated (as you've mentioned).

Re: The lazy Git UI you didn't know you need

#167

Post by mariusor »

johnisgood wrote: post #142
petepete wrote: post #74

Earlier quoted context omitted.

Me too, it’s been my tool of choice for staging hunks for more than 15 years now.

For that, I use git-cola... for some reason. Even though I live in the terminal.

Oh, I didn't know it. It looks pretty useful, but it requires more mouse usage than I'd like and its window is not very well suited for tiled window managers straight out of the box.

Re: The lazy Git UI you didn't know you need

#168

Post by oneeyedpigeon »

nice_byte wrote: post #9

the only good git GUI that exists is Fork. Unfortunately, it doesn't run natively on Linux, although some people have had luck running it under Wine. I found lazygit specifically so bad to the point that I was better off typing in git commands into the terminal manually like some sort of caveman. Somehow, lazygit has found a way to make git even more confusing and user hostile than it already is, which is a significa…

Wow, $60! It had better be really, really good for that price.

I managed to get on fine with lazygit during a quick trial this morning. It actually doesn't have a manual (`man lazygit`: `No manual entry for lazygit`) but I found the contextual help (e.g. press ?) useful.

Re: The lazy Git UI you didn't know you need

#169

Post by yard2010 »

prmph wrote: post #7

You might laugh, but in years of serious development, I have not come across a better git UI tool than SourceTree. If I want to be hard-core, I'd use the original git CLI. SourceTree is unmatched in how it makes using git so much more pleasant for when you need to do something relatively simple, but which would be quite cumbersome to do with the CLI and most other tools I've tried. Its file status and history view is…

Fork is a great alternative to SourceTree!

Re: The lazy Git UI you didn't know you need

#170

Post by oneeyedpigeon »

WolfeReader wrote: post #22
nice_byte wrote: post #9

the only good git GUI that exists is Fork. Unfortunately, it doesn't run natively on Linux, although some people have had luck running it under Wine. I found lazygit specifically so bad to the point that I was better off typing in git commands into the terminal manually like some sort of caveman. Somehow, lazygit has found a way to make git even more confusing and user hostile than it already is, which is a significa…

As much as I heartily disagree with most of what you wrote - and seeing all the downvotes, I'm not the only one - there is a nugget of truth in what you wrote, which answers a lot of your complaints. "Using it was a harsh reminder of what people running emacs or vim for the first time have to go through." The benefit of keyboard-driven programs like Vim is that you're trading an initial learning curve for a vastly mo…

> Mouse-driven tools like VS Code don't demand that the user learns them.

Honestly, I found the barrier to entry way lower with lazygit than with vscode.

I realise I'm not adding anything useful to this discussion. I tried to start VSCode so that I could evaluate it and, maybe, add some info. as to why I find it more difficult to get into, but it just crashes now :shrug:

Post reply on HN