• tinkeringidiot@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    5 months ago

    Nobody knows git. We all just run the few basic commands, then again with the -f switch just in case. Then if that doesn’t work, reclone.

    • Eager Eagle@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      5 months ago

      nonsense - never just delete the project and start fresh. You spend 20min trying to diagnose the problem by searching for the error messages and looking at the manual, then 1h-2h trying different solutions that only make the problem worse up to the point you actually think you lost your changes, then you realize your changes were stashed all along, then you apply them and notice you still have the same original problem. You try a few more commands that get you to a detached head. Then you try to solve a detached head, realizing after 30 min it’s an impossible task, and only then you delete everything and start fresh.

  • technojamin@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    5 months ago

    This was a really good talk! I’ve been using git for about a decade, but I learned several new things. Here’s a few:

    • Sorting git log by committer date
    • Speeding up common operations on bigger repos with git maintenance
    • More useful file blame with the -C flag on git blame
  • Kissaki@feddit.de
    link
    fedilink
    English
    arrow-up
    0
    ·
    5 months ago

    Regarding visual client: I’ve been using TortoiseGit since early on and no other client I’ve tried came close.

    I use the log view and have an overview, and an entry point to all common operations I need. Other tools often fail on good overview, blaming through earlier revisions, filterable views of commits or files, or interactive rebase.