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

Lazygit: Simple terminal UI for Git commands

github.com

Post reply on HN
Print view View original

11–20 of 82 posts

Re: Lazygit: Simple terminal UI for Git commands

#11

Post by tomkarho »

FrontAid wrote: post #4

I use IntelliJ IDEA and often rely on their own Git functionality. But it cannot stage specific lines, only whole chunks [1]. For that, I've been using lazygit for a couple of months now. I like its simple UI and that it makes staging specific lines very easy and quick. If you like lazygit, you might also be interested in similar Git CLI clients that I collected here [2]. [1] https://youtrack.jetbrains.com/issue/IDEA…

Is this something missing specifically from IDEA?

In Rider, there are features that allow committing individual lines instead of a whole file. You can select in the commit dialog which lines to include/omit. Also I recommended taking a look at Changelists feature that allows separating certain changes from what would be committed next (I believe it works line by line basis).

Re: Lazygit: Simple terminal UI for Git commands

#12

Post by williamdclt »

wanderingmind wrote: post #9

Maybe some VSCode users can tell me what specific actions Lazygit do that Gitlens (free version), can't do? And gitlens can do a lot (stash handling, commit revert, branch checkout from remote, autofetch, rebase and many more). Or is it just a different workflow that others find easy to use?

I use VSCode but not git lens. I don't think it does much that Lens doesn't, it's indeed a different workflow for me: I don't like to use the mouse so the clicky-clicky workflow of Lens doesn't work for me, I'm much faster with lazygit (and I can instantly drop to the `git` CLI if there's something I don't know how to do with lazygit, as I'm already in the terminal).

I'm not particularly keen to have my VCS and my code editing in the same software really, although I wouldn't say that it's a superior approach.

Re: Lazygit: Simple terminal UI for Git commands

#13

Post by FrontAid »

tomkarho wrote: post #11
FrontAid wrote: post #4

I use IntelliJ IDEA and often rely on their own Git functionality. But it cannot stage specific lines, only whole chunks [1]. For that, I've been using lazygit for a couple of months now. I like its simple UI and that it makes staging specific lines very easy and quick. If you like lazygit, you might also be interested in similar Git CLI clients that I collected here [2]. [1] https://youtrack.jetbrains.com/issue/IDEA…

Is this something missing specifically from IDEA? In Rider, there are features that allow committing individual lines instead of a whole file. You can select in the commit dialog which lines to include/omit. Also I recommended taking a look at Changelists feature that allows separating certain changes from what would be committed next (I believe it works line by line basis).

I don't know Rider, but I assume this is a limitation in all of their IDEs. Yes, you can commit only certain changes within a file. But you can only do that based on whole chunks. For example, if you add two new lines at the end of an existing file, you cannot commit only one line but not the other. The same limitation applies to changelists (at least in IntelliJ IDEA and Webstorm).

Re: Lazygit: Simple terminal UI for Git commands

#14

Post by hibbelig »

williamdclt wrote: post #12
wanderingmind wrote: post #9

Maybe some VSCode users can tell me what specific actions Lazygit do that Gitlens (free version), can't do? And gitlens can do a lot (stash handling, commit revert, branch checkout from remote, autofetch, rebase and many more). Or is it just a different workflow that others find easy to use?

I use VSCode but not git lens. I don't think it does much that Lens doesn't, it's indeed a different workflow for me: I don't like to use the mouse so the clicky-clicky workflow of Lens doesn't work for me, I'm much faster with lazygit (and I can instantly drop to the `git` CLI if there's something I don't know how to do with lazygit, as I'm already in the terminal). I'm not particularly keen to have my VCS and my co…

My personal take: I like using the keyboard. Lazygit works very smoothly with the keyboard, of course.

I tried the git thing that’s part of vscode and it really wants me to click. It is theoretically possible to get by without, but it’s cumbersome.

Re: Lazygit: Simple terminal UI for Git commands

#16

Post by wanderingmind »

williamdclt wrote: post #12
wanderingmind wrote: post #9

Maybe some VSCode users can tell me what specific actions Lazygit do that Gitlens (free version), can't do? And gitlens can do a lot (stash handling, commit revert, branch checkout from remote, autofetch, rebase and many more). Or is it just a different workflow that others find easy to use?

I use VSCode but not git lens. I don't think it does much that Lens doesn't, it's indeed a different workflow for me: I don't like to use the mouse so the clicky-clicky workflow of Lens doesn't work for me, I'm much faster with lazygit (and I can instantly drop to the `git` CLI if there's something I don't know how to do with lazygit, as I'm already in the terminal). I'm not particularly keen to have my VCS and my co…

Thanks that makes sense especially for folks that use keyboard and like to do it within CLI.

Re: Lazygit: Simple terminal UI for Git commands

#17

Post by williamdclt »

williamdclt wrote: post #12
wanderingmind wrote: post #9

Maybe some VSCode users can tell me what specific actions Lazygit do that Gitlens (free version), can't do? And gitlens can do a lot (stash handling, commit revert, branch checkout from remote, autofetch, rebase and many more). Or is it just a different workflow that others find easy to use?

I use VSCode but not git lens. I don't think it does much that Lens doesn't, it's indeed a different workflow for me: I don't like to use the mouse so the clicky-clicky workflow of Lens doesn't work for me, I'm much faster with lazygit (and I can instantly drop to the `git` CLI if there's something I don't know how to do with lazygit, as I'm already in the terminal). I'm not particularly keen to have my VCS and my co…

> I'm not particularly keen to have my VCS and my code editing in the same software really, although I wouldn't say that it's a superior approach.

Addendum: I'm also not always using VSCode. Sometimes I just use vim if I'm already in my terminal and it's a small edit, at which point I don't want to have to go back to VSCode (potentially having to open the project) just for git

Re: Lazygit: Simple terminal UI for Git commands

#19

Post by xuhu »

parentheses wrote: post #5

I found lazygit after building something of my own thay solves some of these problems for me - git-fuzzy [0]. I'd like to share some of my thoughts about the comparison. lazygit is a TUI for git which can behave in a standalone fashion. It's also designed to be quick and easy to use to perform quite advanced actions but ones that a seasoned git user may really want when working with git history. Since I'm already a s…

Of tools that mash interactive GUIs (lazygit) with scriptable shells (git fuzzy), I only know of AutoCAD. Scripts would routinely ask you to interactively select a set of points or an item in a list.

Are there other apps that offer scriptable GUIs ?

Re: Lazygit: Simple terminal UI for Git commands

#20

Post by IggleSniggle »

williamdclt wrote: post #17
williamdclt wrote: post #12

Earlier quoted context omitted.

I use VSCode but not git lens. I don't think it does much that Lens doesn't, it's indeed a different workflow for me: I don't like to use the mouse so the clicky-clicky workflow of Lens doesn't work for me, I'm much faster with lazygit (and I can instantly drop to the `git` CLI if there's something I don't know how to do with lazygit, as I'm already in the terminal). I'm not particularly keen to have my VCS and my co…

> I'm not particularly keen to have my VCS and my code editing in the same software really, although I wouldn't say that it's a superior approach. Addendum: I'm also not always using VSCode. Sometimes I just use vim if I'm already in my terminal and it's a small edit, at which point I don't want to have to go back to VSCode (potentially having to open the project) just for git

I thought I was a weirdo for splitting my usage between VSCode and nvim. I do the same! And I don't even use any fancy vim features. I think it's a mental separation for me: "right now, I am doing sysadmin stuff and need to have my sysadmin brain on" vs "right now, I am developing software and need to have my software brain on", but I'm not even really sure about that.
Post reply on HN