6 ms·
I’m generally very skeptical of anything that abstracts away git with UIs. This looks really cool though and I like that you embedded common git workflows into
by vardaro 6y ago
I’m generally very skeptical of anything that abstracts away git with UIs. This looks really cool though and I like that you embedded common git workflows into the CLI
- acemarke 6y agoOn the flip side, I'm a strong proponent of using a GUI for many Git tasks: https://blog.isquaredsoftware.com/2021/01/coding-career-git-usage/#git-tools https://blog.isquaredsoftware.com/2021/01/coding-career-git-... but I also use the CLI for other tasks as well. For example, it's _way_ easier to add specific file chunks or individual lines to the staging area via a GUI, or do interactive rebasing.
- scns 6y agoI concur. Intellijs git client alone makes it hard for me to even imagine using something else. Read a comment on HN where someone use only the git client from it.
- oxinabox 6y agoStrong agree. I will use the command line for basics, commit, push, pull, simpler rebases. But it I am going to be cherry picking a commit onto a backport branch, or splitting up one branch into two, or doing an interactive rebase, or (as said) committing some parts of s file but not others, I want a GUI
- cturtle 6y agoI almost always default to git add -p when staging (and git reset -p when needed). Git rebase -i also feels very quick to me as well. When isolating just one line from many changes the gui is nice, but in the majority of cases the CLI is much faster (no need to scroll in long files to find the next hunk)
- bsoft16385 6y ago+1 to this. I mostly use the CLI, but it's really nice in my IDE (JetBrains Rider) to be able to browse version history or resolve merge conflicts graphically.
- skrebbel 6y agoYeah a mouse would be a terrible way to interact with a graph!
- iamatologist 6y agoThis is not really an abstraction.