• AVincentInSpace@pawb.socialEnglish
    3·
    11 months ago

    Every time I commit I have to look through git diff, figure out what the hell I actually did, come up with something intelligent to say about jt, possibly split the commit into multiple commits if I changed multiple things, do some shuffling with git reset and git add…

    For some reason all my personal projects are all like 4K SLoC with 50 total commits, all of which include apologies for not doing more smaller commits

    • SokathHisEyesOpen@lemmy.mlEnglish
      2·
      11 months ago

      There’s a bigger issue than your commit message if you don’t even know what you just coded and are committing.

      • akkajdh999@programming.dev
        2·
        11 months ago

        I just get too excited about actually implementing/fixing something (random things that I see along the way) more than commit ceremony (nobody will care about it in my project anyway other than one random guy who gave the repo a star)

        • oce 🐆@jlai.lu
          2·
          11 months ago

          Nah, I’m that guy, I gave your repo a star for the effort, but I’m not reading your history.

      • AVincentInSpace@pawb.socialEnglish
        1·
        11 months ago

        You see, sometimes I code something, go to bed before finishing it, come back, decide not to commit because then I’d have to think of a commit message and I just want to code, start working on an unrelated feature, do that for a couple days, get distracted by life stuff and put the project down for a few weeks/months, rinse and repeat, and then I finally get around to writing a commit message because I’m about to start a huge change and I want a restore point and I’m like. Okay, it’s been like 3 months since my last commit, I’m pretty sure my code can now do something it couldn’t 3 months ago but come on, I can’t even remember what I had for lunch last Thursday

        I’m well aware this is terrible practice but I don’t know how to stop doing it

        • dukk@programming.dev
          2·
          11 months ago

          Commit more often. Maybe work in a different feature branch, and don’t be afraid to commit your half-working crappy code. If it’s a personal project/fork, it’s totally acceptable to commit often with bad commit names and small unfinished changes: you can always amend/squash the commits later. That’s how I tend to work: create a new branch, work on the feature, rebase and merge (fast forward, no merge commit). Also, maybe don’t jump around working on random features :P

        • PoolloverNathan@programming.devEnglish
          1·
          11 months ago

          Patch add - it shows you particular changes you made, and you choose whether or not to include them in the commit. (You can then use git stash -k to stash only the changes you did not add, so you can test before you commit.)

  • syd@lemy.lol
    2·
    11 months ago

    I’m using Copilot for it right now. It works on half of the cases.

      • foxymulder@lemmy.mlEnglish
        1·
        11 months ago

        “patch mode” - Patch mode allows you to stage parts of a changed file, instead of the entire file. This allows you to make concise, well-crafted commits that make for an easier to read history.

  • catastrophicblues@lemmy.ca
    1·
    11 months ago

    Oh god I feel so called out. I wish I paid more attention to my commit messages but I’m usually too busy fixing the directory structure and refactoring. Sigh.

    • brlemworld@lemmy.world
      1·
      11 months ago

      My company collapses into a single commit at merge so idgaf what the commit message is anymore. Though I would prefer not collapsing them.