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

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

    • solariplex@slrpnk.net
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      I use it as well! Not sure if it’s a flatpak thing, but for some reason I need to re-enter credentials for my git remotes for each push. What’s your experience?

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

  • CosmicBlend@kbin.social
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    I used to use SourceTree but it runs horribly and switched to Fork years ago and never looked back. I use VSCode for merge conflict resolution.

  • Orvanis@lemm.ee
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    TortoiseGit user here. Love that it integrates with Windows Explorer so I don’t have to constantly be opening an app first to fire off some Git commands.

  • sunaurus@lemm.ee
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    I use a 50%-50% mix between git CLI and the built-in git tools in JetBrains IDEs.

    To be honest, I could quite easily get by with just the JetBrains GUI - they have a super sophisticated GUI that can easily handle things like interactive rebase, cherry-picking, etc + they have a great conflict resolution tool. I just use the cli every now and then if I want to get something done quickly while I don’t have an IDE window open.

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

      This one. It’s sophisticated and easy to navigate.

      I generally do conflict resolution in Jetbrains IDEs and everything else in CLI. Occasionally, I might commit from the IDE if I only want a single file.

    • arandomthought@vlemmy.net
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      I mostly use the CLI but when I used to use PyCharm the JetBrain git GUI was the shit. The closest to it in a standalone program I’ve seen is maybe sublime merge, which is also great.

  • exu@feditown.com
    link
    fedilink
    arrow-up
    4
    ·
    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
      1
      ·
      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.

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

    No, I find typing faster than clicking and I’ve been using git for so long the commands are second nature to me.

    • Chrissie@discuss.tchncs.de
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 year ago

      What I prefer most about having a UI is the better sense of overview over the repository and it’s branches.

      I find, when compared to people I’ve worked with that prefer plain git, that I’m much quicker at finding certain changes or seeing what is in which branch with GitExtensions.

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

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

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