What do you prefer? and why is it CLI? 😅

@GithubProjects CLI because it supports all commands and gets the latest updates

To be honest, I use both. The Git CLI is great, but I had a hard time memorizing less frequently used commands. No problem with standard commit/push. However, with an AI-based terminal like @warpdotdev, it's now much easier due to AI autocompletion. Yes, I now use both options, even the integrated one in VSCode. So basically three options.😉

@GithubProjects git cli, will not fall for the GUI psyops

@GithubProjects CLI's power is undeniable, but GUIs unlock accessibility for wider adoption.. future is both, thoughtfully integrated..

@GithubProjects definitely the cli :)

@GithubProjects I can't figure out the desktop version and I don't like the interface reporting.

@GithubProjects Forever CLI

@GithubProjects CLI… I see too many devs try to learn Github Desktop and other UI applications. CLI rarely changes so its learn once and you’re off no matter the OS

@GithubProjects GitHub desktop for the win

@GithubProjects CLI anyday I like doing things quick with keyboard, and CLI has better UX for keyboard users

@GithubProjects CLI is for the pros

@GithubProjects Neither, unless I'm forced to. The only reasonable way to visualize SCM history, near and far, is with a GUI that shows branches. Anything else is a waste of time. So, SourceTree or Git Extensions.

@GithubProjects And then there's Github CLI, which is just Github Desktop rebranded for the terminal but adds a few features but still isn't as good as git CLI

@GithubProjects There is a desktop version?! 😳

@GithubProjects Recently using @gitbutler

@GithubProjects Reason: cli is cli

@GithubProjects Because CLI makes you feel like a hacker. 😂

@GithubProjects yes, CLI is so powerful and easy (kan?)

@GithubProjects I am making commits directly from the browser 🤝 (no it's not next level of being turd, it's actually the most user friendly way to hit some change fast from any device) - love it

@GithubProjects Because it's where you actually build things. Anything else is just extra steps.

@GithubProjects I've never used GitHub Desktop and I have no reason to try it. I understand git and I'm already in the terminal anyway. Why do I need to add another UI app into the mix?

I’ve been CLI for years now. I can never use a desktop client for git. My brain just doesn’t work that way. I’ve tried GitHub desktop. Even if my IDE had great git integration for commits, I would still switch to my CLI. Besides, with modern tools like @warpdotdev it’s so easy peasy it’s not even a question. I think people who still stick to desktop tools slow down their workflow by 10-20x at least!

@GithubProjects I prefer GitHub Desktop too — clean, visual, and easy to manage everything without hassle. ✅

@GithubProjects cli is for the real devs

@GithubProjects Because Copilot can drive with it in agent mode

@GithubProjects I don't trust anyone doing commits via their IDE or any git GUI app

@GithubProjects CLI pleasee.

@GithubProjects SmartGit..

@GithubProjects true

@GithubProjects Cli

@GithubProjects github.com/desktop/deskto…

@GithubProjects magit + cli

@GithubProjects Gh

@GithubProjects tbh, desktop-version is more comfortable, especially with the differ 🤭