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.

    • BentiGorlich@thebrainbin.org
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      I am using it too and I love it. I only know source tree as a competitor and in comparision it sucks…

      You dont have to pay for it, even when using it comercially (unpess they changed that)

      • Modal@lemmy.sdf.org
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        1 year ago

        It has a “free evaluation” that I think can be as long as you want it to be / honor system.
        Its been worth it to me to pick up a license and support the development though. Its reasonably priced (for a dev tool) / no subscription and definitely beats the free clients I was using before (Sourcetree/GithubDesktop).

  • davehtaylor@beehaw.org
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    I have some git blame extention in VSCode, but otherwise no. Something about using gui tool for git makes me feel so disconnected from it, like I’m not entirely sure what’s going on, and afraid I’m going to fuck something up

    Also, I forget commands all the time. Mostly ones I don’t use often, like changing/adding/removing remotes, changing settings, etc.

  • s_w@beehaw.org
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    I use IntelliJ’s built-in git GUI.

    I don’t understand why people use command line only. Sure, learn the commands so if you need to use them you can, but most GUIs are far more feature rich than command line. With IntelliJ, I can easily view differences before committing, have it do code quality scans, automatically clean up any code it can, more easily choose which files I want to commit vs the typical ‘git add .’ I see most people do with command line, have separate changelists when pair programming, and much more.

    One argument that continually comes up is that command line is faster. I completely disagree. If I want to just commit the code without reviewing it, I can use 2 hot keys and the code is committed and pushed. But as I do a quick readthrough of all the code first and review issues from the code quality analysis it does take more time, but still less than it would to do comparable things with command line.

    • dbanty@beehaw.org
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      The IntelliJ merge UI is the only way I ever want to deal with merge conflicts. So much better than any of the alternatives I’ve tried!

    • pinkpatrol@anarch.is
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      I’m a heavy intellij user, but the git log UI always confuses me. When I open ‘git log’ via the action menu IntelliJ doesn’t focus my current branch. I am not sure if there’s some other menu I’m supposed to use to achieve that.

      I do use the commit local changes, pull changes, merge branches functionality a good bit. My only feedback there is that I haven’t found a way to quickly commit changes without running git hooks. Each time it requires me to open up the gear icon and deselect ‘git hooks’. This is slower than using the command line where I can write git commit --no-verify and repeat the same command again and again. I know it’s a niche need, but it’s necessary for testing a rather archaic system we maintain.

  • Chrissie@discuss.tchncs.de
    link
    fedilink
    arrow-up
    3
    ·
    1 year 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.

  • danknodes@kbin.social
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    VS 2022 is finally somewhat usable for Git using the git Changes pane. The whole team uses it this way, and for many of them it’s a first for git as well.

  • thepaperpilot@beehaw.org
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    I use sublime merge because I really like ST and want to further support the dev. I wish it had more integrations with github (and theoretically github alternatives), but I understand the reasoning not to. Before SM came out I just used the command line exclusively.

    • pkulak@beehaw.org
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      I never use Sublime Text, but I love Sublime Merge. I dunno why. Something about the UI just works for my brain, and the merge UI is amazing. I only ever open it with smerge . in a directory, and it’s set to floating in my window manager so it pops up, I do my thing, and it goes away.

  • sznio@beehaw.org
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    I use the VS Code built-in git support for making commits, and fall back to the CLI for anything else.

    You won’t have trouble remembering commands once you use them often enough. And you don’t need to know all of them, just the ones your workflow uses. My toolbox is commit, checkout, status, reset, rebase -i, merge, bisect. That’s all I need day-to-day.

  • exu@feditown.com
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    Magit with emacs (doom emacs to be fully honest). More a TUI, but definitely fully keyboard driven :)

  • vraylle@kbin.social
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    1 year ago

    I actually like the tooling built into VS Code. Added the GitHub Pull Requests and Issues extension for the PRs, pretty happy with it all at the moment. Before that I like a specific older version of SourceTree that didn’t forget your credentials.