41
submitted 2 years ago* (last edited 2 years ago) by lysy@szmer.info to c/programming@beehaw.org

I ask because I like console, but at the same time have difficulties remembering all the commands. I'd like to try a GUI that is comfortable to use with only a keyboard.
[edit]
My inbox got fediversized, fantastic feeling.

(page 2) 50 comments
sorted by: hot top controversial new old
[-] postscarce@kbin.social 2 points 2 years ago

I use GitHub Desktop for 95% of my git needs, terminal for the other 5%

[-] alottachairs@beehaw.org 2 points 2 years ago

Github desktop is the only way I know how to clone my private repo. I do not understand how to clone my private repos through CLI.

load more comments (5 replies)
[-] narc0tic_bird@beehaw.org 2 points 2 years ago

I use a mix of CLI, the Git UI built into VSCode, and Sublime Merge.

Sublime Merge is great for getting an overview, it's very snappy (especially when compared to Electron Git UIs), and I love the merge conflict editor. It's not cheap, but worth every penny.

[-] arandomthought@vlemmy.net 1 points 2 years ago

Isn't it free if you're okay with using it in light mode?

[-] narc0tic_bird@beehaw.org 1 points 2 years ago

Well, you can technically use it for free, but that doesn't make it licensed properly. It's like the infinite WinRAR trial kind of.

[-] taigaman@kbin.social 1 points 2 years ago* (last edited 2 years ago)

That's what I do. It works out pretty well. I'd really like to buy from them at some point.

[-] Xanvial@lemmy.one 2 points 2 years ago* (last edited 2 years ago)
load more comments (1 replies)
[-] lijenipenzic@beehaw.org 2 points 2 years ago

Would it work for you if you created git aliases for commands you can't remember?

[-] james@lemmy.jamesj999.co.uk 2 points 2 years ago

I generally don't trust most git GUIs - a number of our developers have used SourceTree on OS X before and it's led to nothing but issues. The only one I trust is the one built into IntelliJ IDEA, otherwise I'll use commandline.

[-] evolatic@beehaw.org 2 points 2 years ago

I use GitKraken. It has a beautiful interface. It's free to use non-commercially but I pay $50/yr so that it can connect to my companies Enterprise account. I know I'm weak with git (I get the concepts but I'm a visual person) so the money is worth it to me.

load more comments (1 replies)
[-] frozen@lemmy.frozeninferno.xyz 2 points 2 years ago

I use VSCode for simple commits and merge conflicts. Anything more complicated and I go to CLI since it's usually better documented.

[-] Unimeron@feddit.de 2 points 2 years ago

KDE has a relatively new git tool named Kommit: https://apps.kde.org/de/kommit

[-] ChrissieWF@discuss.tchncs.de 2 points 2 years ago

Developing in a Windows environment, I generally prefer Git Extensions.
It doesn't distract the eye with unneeded fancy and is very close to a command line git experience but still allows me a better visual sense of the repository and branches.

[-] Notyocheese@kbin.social 1 points 2 years ago

I use Git Tower and I love it. I'm surprised I don't see it mentioned here.

[-] thekerker@kbin.social 1 points 2 years ago

I kinda do both? For some reason, I prefer the CLI when I clone a repo, but Sourcetree for committing, pulling, and pushing, and my IDE's built in git tools for merges.

[-] Elbullazul@lem.elbullazul.com 1 points 2 years ago

I mostly use the CLI, but I occasionally use fork when a GUI is needed

[-] Frederic@beehaw.org 1 points 2 years ago

I mostly use CLI but sometimes SourceTree, it's neat

[-] Perry@kbin.social 1 points 2 years ago

JetBrains have some quite extensive VC tooling built into their IDEs which I use almost exclusively. I used to do everything in the terminal, but I find it so much quicker and simpler to do it directly in the IDE.

[-] Lells@kbin.social 1 points 2 years ago

I use GitKraken, which is pretty great, but for a lot of day to day stuff I just end up using the CLI

[-] Rumble@kbin.social 1 points 2 years ago

We use this at work too. I have to say Fork is really great too, but there is no linux version.

[-] terribleplan@lemmy.nrd.li 1 points 2 years ago

I own sublime merge because it was cheap when I upgraded to ST4, but never use it. It's not bad or anything, but honestly the CLI is more convenient to use (and all the GUIs I've used have a lot of clicking involved). I don't know that you're going to find something better than the CLI, especially given your requirement ow "comfortable to use with only a keyboard".

[-] jadero@lemmy.ca 1 points 2 years ago

I don't have a recommendation, but I understand the desire for excellent keyboard support in a GUI. I switched to Linux after 3 decades on Windows and I really miss doing all the screen navigation from the keyboard. In Windows, the only time I used a mouse was inside things like drawing tools and badly written apps with inadequate or non-standard keyboard support.

[-] MeowdyPardner@kbin.social 1 points 2 years ago

Not really but sometimes if I need a visualization of something complicated that I can't see in my head I'll go to the network tab under insights in github

[-] syphe@kbin.social 1 points 2 years ago

Git extensions, have been using it for years, and while the UI is not flashy, it gets the job done really really well.

[-] giloronfoo@beehaw.org 1 points 2 years ago
  • 45% SourceTree
  • 45% CLI
  • 10% TortoiseGit

The repository I work in is huge, old, and the folder structures are wide and deep. It is normal to modify tens of files in almost as many folders for a single feature change.

SourceTree for managing staged files and committing.

CLI for pull, branch switching, and searching.

TortoiseGit for showing the log or blame of individual files and folders.

[-] potato@lolimbeer.com 1 points 2 years ago

While I do most actions with the git command or the git fugitive plugin from tpope, I will sometimes whip out lazygit for certain things I don’t do that often.

https://github.com/jesseduffield/lazygit

load more comments (1 replies)
[-] ptz@dubvee.org 1 points 2 years ago* (last edited 2 years ago)

"No. No, man. Shit, no, man. I believe you'd get your ass kicked, sayin' somethin' like that, man." - Office Space

That said and jokes aside, occasionally I'll use the integrated git in vscode but mostly use the terminal. I do recommend a Git cheat sheet to help become more proficient with the CLI interface.

~~Atlassian~~ Github Git Cheatsheet: Changed to the Github version as the Atlassian one was an auto-downloading PDF.

[-] lysy@szmer.info 1 points 2 years ago

Funny that I haven't thought about cheatsheet, even though I use one for vim ^_^'

[-] ppb1701@kbin.social 1 points 2 years ago

@lysy SourceTree. Tabs for multiple repos, history search and a gui view of the branch(es). Integrates without a lot of trouble.

[-] SkepticElliptic@beehaw.org 1 points 2 years ago

You can set aliases for CLI.

[-] dracul104@lemmy.sdf.org 1 points 2 years ago

I mainly program in Visual Studio so I use it's integration for simple commits, diffs, and checkouts. Anything more complicated than that I head for the command line.

[-] CaptainJack42@discuss.tchncs.de 1 points 2 years ago

Haven't seen it mentioned here, I've recently been using lazygit from time to time and I quite like it, especially committing only a few changed lines from a file is nice and quickly amending to old commits. I still use cli for more complicated stuff though.

[-] kriss0706@kbin.social 1 points 2 years ago

I use GitHub Desktop - offered by GitHub themself. Its a GUI application where you can fetch, push, pull etc. But mostly just basic github "commands".

https://desktop.github.com/

load more comments
view more: ‹ prev next ›
this post was submitted on 20 Jun 2023
41 points (100.0% liked)

Programming

13473 readers
1 users here now

All things programming and coding related. Subcommunity of Technology.


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS