Live data from Hacker News

Lazygit: A simple terminal UI for Git commands

github.com

131–140 of 143 posts

Re: Lazygit: A simple terminal UI for Git commands

#131
post #87

If there is one thing that terrifies me it's using Git, or any source control, from the command line. No matter how long I've been in this industry, I just can't get cozy with doing a lot of heavy lifting in any shell environment. Give me the GUI all day every day.

I know this is going to sound elitist, but it always bothers me to see comments like this that make it seem like it's okay to not learn how computers work even though you're a software developer (which I'm assuming you are). The command line isn't some mystical scary thing, it's a extremely effective method of controlling a computer. It's survived this long for a reason, and it's not going to go anywhere. It's powerf…

I think most of the aversion towards the terminal comes from how easy it is to screw up things with it as well. There are hundreds of horror stories where one missing "-" or some other character ended up nuking people's entire works and databases worth many hours. Having a GUI gives a buffer and dramatically lowers the chances of doing things that you didn't intend to do.

Re: Lazygit: A simple terminal UI for Git commands

#132
post #87

If there is one thing that terrifies me it's using Git, or any source control, from the command line. No matter how long I've been in this industry, I just can't get cozy with doing a lot of heavy lifting in any shell environment. Give me the GUI all day every day.

I know this is going to sound elitist, but it always bothers me to see comments like this that make it seem like it's okay to not learn how computers work even though you're a software developer (which I'm assuming you are). The command line isn't some mystical scary thing, it's a extremely effective method of controlling a computer. It's survived this long for a reason, and it's not going to go anywhere. It's powerf…

Another aspect of this is that people will never really learn Git with a GUI and all these aliased commands. I'm not against aliases and I use them, but only on software that I'm very familiar with. Developers who are afraid of Git need to sit down and read Pro Git and learn the most commonly used commands, and use a quality reference for the more obscure ones.

Re: Lazygit: A simple terminal UI for Git commands

#133

Can lazygit help me clean up my branches? Our GitHub is set to delete a branch whenever we squash merge it in a PR. But for the life of me I cannot get my local version to cleanup too. All the stack overflow popular answers that use sed and such fail for some reason.

git trim?

If you meant this: https://github.com/foriequal0/git-trim

Thank you! Didn't know about it and it solves the problem I'm having.

Re: Lazygit: A simple terminal UI for Git commands

#134

Looks pretty great, but: Error! Your Xcode (13.0) is too outdated I don't have the luxury of upgrading yet. This requirement seems overly fussy and opinionated.

So download a binary instead of building it from source?

Came here to whine, got a what seems in retrospect to be a perfectly obvious and simple _solution_. Thank you!

Re: Lazygit: A simple terminal UI for Git commands

#135
post #49

Looks pretty great, but: Error! Your Xcode (13.0) is too outdated I don't have the luxury of upgrading yet. This requirement seems overly fussy and opinionated.

I believe that's coming from homebrew itself, which is pretty aggressive about updating everything. The homebrew formula contains no reference to xcode version, for example: https://github.com/Homebrew/homebrew-core/blob/master/Formul...

Good call. Thanks!

Re: Lazygit: A simple terminal UI for Git commands

#136

I maintain a bunch of git aliases in my .gitconfig for my company's rebase based workflow. They cover 90% of my 'dumb' git usages synced = pull origin master --rebase. # Update myself with master squash = rebase -i origin/master # Let me optionally squash whatever has happened since master publish = push origin HEAD --force-with-lease # Save to orig in (github) pub = push origin HEAD --force-with-lease # Save to orig…

> ammend = commit --amend # I cannot spell this word for the life of me

This reminds me of one of my favorite silly aliases, which requires declarations in both my shell profile and my .gitconfig:

In .bashrc : `alias gits=git`

In .gitconfig : `[alias]` `tatus = status`

This allows me to mistype `git status` as `gits tatus` and brings me a small amount of joy.

Re: Lazygit: A simple terminal UI for Git commands

#137
post #65

Earlier quoted context omitted.

I use magit in emacs and I can create any commit I want by slicing out a bunch of characters in a diff. The git CLI is workable for a lot of things,but the experience of higlighting an arbitrary block of text and saying "commit THIS" has not been matched in any other git UI. We're not talking about hunks or lines here, but literally committing an abitrary range of characters.

> committing an abitrary range of characters Honest question: what is the practical use case for this? I'm a fan of small, atomic commits but I don't recall ever wanting to commit just a range of characters.

I use it quite a lot to stage a subset of a change, and then drop the rest of it. In that sense, it's like an overpowered undo tool that helps me keep a change I want without having to rewrite the whole thing.

Re: Lazygit: A simple terminal UI for Git commands

#138
post #88

Earlier quoted context omitted.

It’s more like using hamburger helper instead of a spice rack, a GUI can be excellent and better than CLI, beef isn’t always better when it’s overcooked.

> a GUI can be excellent and better than CLI A unicycle can also be better than a car. Doesn't mean anyone should ever choose a unicycle over a car (unless you're a clown I guess)

If you prefer imagemagick to photoshop.

Re: Lazygit: A simple terminal UI for Git commands

#139
post #124

Was hoping lazy git would perhaps help with a feature that tig lacks and I've only found via vim-fugitive. I.e. viewing the whole file between revisions https://s.natalian.org/2021-12-01/git-file.mp4

IntelliJ's git view can do this too. You can select a file, view its complete history, and view a diff between any two revisions, as well as see the complete state at any revision. And the commit messages are in a subframe.
Post reply on HN