Today I did a git push --force, then I had to create a branch out of the old code, but other times I had to save the files I worked on, delete the local repository, git clone again, then reapply my fixes. I want to at least have a bookmark on how to fix things in the future.

Yes, I’ve heard about VSCode plugins, that supposed to help. But no, I don’t want to use a glorified webpage to do coding, regardless if it’s directly tied to Micro$lop, or some of the slop was removed by 3rd parties. I tried KATE once, I cannot go back to some sluggish webpage, which only argument for use at the moment is “but it has plugins”.

  • ZILtoid1991@lemmy.worldOP
    link
    fedilink
    arrow-up
    0
    ·
    23 days ago

    I want to learn about that specific issue rather than spending months with learning less often used features of a software. People generally don’t master all the available functions of a software before touching said software. Maybe in the sixties-seventies, but not anymore. And there’s also the issue of people forgetting stuff, which will happen when my main interaction with git is pull and push.

    • Noctambulist@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      23 days ago

      You do realize that you don’t have to read a documentation from beginning to end, don’t you? But for that specific feature you need and don’t know how to use—RTFM!