• maegul
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 months ago

    You can just diff two commits on the cli with git diff commit1 commit2 but I guess that what you mean is that you might not have any specific reference two either of the commits so you have to browse through the log to find the commit message that describes the commit, which I’ll grant you is easier in a gui because you have two variables that you have to copy and paste if you’re in the terminal.

    Yea, this is what I’m talking about. When all of the visual affordances coalesce into a pretty simple flow.

    And to be clear, I’d suspect many like myself end up using both, where there’ll always be some shortcoming in any given GUI that only the CLI can fill functionality/power wise. But defaulting to a GUI (or even a good TUI or editor plugin) for everyday usage, like I said, makes sense.

    • zygo_histo_morpheus@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      2 months ago

      Like you say, there are always gonna be particular cases where gui/cli is better but for the general case I think it has to do with if your workflow is more terminal or gui oriented in general. I think that many of the tradeoffs in gui/cli git aren’t really unique to git so I think sticking with your general preference in that are makes sense.

      Since I’m a vim user (shocking, I know) I actually use git through the fugitive plugin a lot, but it’s a fairly thin wrapper around the cli interface so most things are pretty much just the same as using the cli except that you can call them as vim commands instead (:Git push instead of git push and so on)