I use the right tool for the job, always. If all I need is to push a branch, then I’d rather use a UI that quickly shows me the changes in a nice diff layout. If I’m doing a pull request review and want to run it locally, I select the branch, pull, and go.
That said, when there are conflicts or tricky merges, or I want to squash a bunch of commits, anything like that, I’ll use the CLI.
It’s not about being above GitHub desktop or being an enlightened CLI user. It is about using the tool that is needed.
I’ve only been writing and releasing software for 15 years, what do I know.
That said, use whatever workflow fits you best! If that’s your hands never leaving the keyboard, rock on! If you instead write code like you’re playing an FPS, enjoy! We all do this because we like it, right? 😊
Who the fuck codes and is such a terrible coder they are using shitty GitHub desktop?
You can be a perfectly good dev and not enjoy working in the cli, especially when there are good enough alternatives
GitHub desktop is the first thing I recommend whenever someone ducks up their local repo by using eclipse’s git integration.
It’s so easy even an eclipse user can solve their issue by clicking a simple “sync” button. They don’t need to even know how git works.
That’s literally the problem being talked about. You need to know how git works to avoid these kinds of problems.
Beginners, probably? I agree it sucks tho, bundling a whole ass browser just for some fancy semi-automated
gitexecutionshehe.
Why you haff to be mad its only preference
https://youtu.be/xzpndHtdl9A?si=TNH0CnrAXrrUM3ae
Right here, brother.
I use the right tool for the job, always. If all I need is to push a branch, then I’d rather use a UI that quickly shows me the changes in a nice diff layout. If I’m doing a pull request review and want to run it locally, I select the branch, pull, and go.
That said, when there are conflicts or tricky merges, or I want to squash a bunch of commits, anything like that, I’ll use the CLI.
It’s not about being above GitHub desktop or being an enlightened CLI user. It is about using the tool that is needed.
I’ve only been writing and releasing software for 15 years, what do I know.
That said, use whatever workflow fits you best! If that’s your hands never leaving the keyboard, rock on! If you instead write code like you’re playing an FPS, enjoy! We all do this because we like it, right? 😊