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
      3
      ·
      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
        2
        ·
        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).

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

      Came here to recommend it too, really neat and practical tool and I haven’t found a better alternative yet. Honestly I don’t know why are people so against GUI git tools, it makes visualizing branches and commits so much more easier. I don’t think you can use it only with your keyboard as OP asked though, dunno how important that is to them.

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

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

    • dolle@feddit.dk
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Same here. I don’t even use emacs for development anymore (I use IntelliJ since all my work is on the JVM and Typescript) but I still have an emacs running in the background for magit and org-mode. Magit is insanely effective for performing complex rebasing and cherry-picking tasks.

  • Djoot@feddit.dk
    link
    fedilink
    arrow-up
    5
    ·
    1 year ago

    Lazygit changed how I use git, it is so easy to do all the daily essentials like branching, committing, and merging, but also also does more advanced things like interactive rebasing when needed.

    I had searched for a proper git client, that was free and open source plus worked on both Linux and Windows, for a long time and I haven’t looked back after finding lazygit.

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

    These days I can run everything I need to with the git cli. I use the JetBrains visual merge tool to resolve conflicts, because doing that by hand is so awfully error prone, it very very intuitively maps to a visual process

  • s_w@beehaw.org
    link
    fedilink
    arrow-up
    5
    ·
    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.

    • knaugh@frig.social
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      as an idiot, I tend to click around without thinking. You don’t need to understand what you’re doing as much with a gui. When I started using the command line I started having a lot less problems, lol

    • 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.

    • 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!

  • evolatic@beehaw.org
    link
    fedilink
    arrow-up
    4
    ·
    1 year 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.

  • danknodes@kbin.social
    link
    fedilink
    arrow-up
    4
    ·
    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.

  • Admiral Patrick@dubvee.org
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    1 year 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.

  • sznio@beehaw.org
    link
    fedilink
    arrow-up
    4
    ·
    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.

  • frozen@lemmy.frozeninferno.xyz
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

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