|
wifi said @retoor If you're a solo developer working on your side project, there's no need for a GUI.
|
|
|
|
But if you're working in a team on projects where repos can quickly spread into several feature branches which were built from an unmerged branch because that one feature wasn't approved yet, then you should be super careful.
|
|
|
|
Yes I'm talking about conflicts.
|
|
|
|
You can't just run commands in your CLI and go to bed. Conflicts have to be manually reviewed and resolved, and GUIs display these in a nice way. They also run safe git commands and flags that you probably don't know.
|
|
|
|
In the end I do less typing and I'm quicker.
|
|
|
|
I'm not using a GUI because I don't know how to use the CLI. I'm using it for safety and reliability. I have run commands (by accident) in the CLI before. Never in a GUI.
|
|
|
|
The team lead in question has been a dev for more than 15 years, but commits still go missing after they attempt to resolve a conflict with their almighty CLI.,JetBrains IDEs don't do this. It only undoes changes in the current file.
|
|
|
|
I heard WebStorm is now free for non-commercial use.
|
|
|
|
Source: I use it for work.
|
|
|
|
I use VSCode for personal projects bu never really paid attention to this.,@typosaurus
|
|
|
|
If those are the only things you do with git, then you don't need a GUI.
|
|
|
|
In my case, we have structures and rules. Every feature, request, or change must have single logical commits in master (for easy reverts).
|
|
|
|
Example: If you were working on request 1234 (built from a parent unmerged & unaproved branch 1233), and your colleague needed to update branch 1233, now you eventually have this commit tree.
|
|
|
|
1234 - Footer widgets design
|
|
|
|
1233 - Fix header css
|
|
|
|
1234 - Build footer components
|
|
|
|
1234 - Integrate footer API
|
|
|
|
Knowing that the goal in the end is to have one single commit for each request in master, How do you quickly "squash" all your 1234 commits into one?
|
|
|
|
In a GUI I can do this in less than 5 seconds.
|
|
|
|
I know how it's done in a CLI, I just prefer not to add that extra stress to my life.,I haven't been here often, but is it possible to display images here inline? Is there even any kind of formatting in this body text?
|
|
|
|
**markdown test**
|
|
|
|
<b>html test</b>,Gemini API key visible in client.
|
|
|
|
If that was a pay-as-you-go plan, you could be in debt quickly.``` |