• Deebster@programming.dev
    link
    fedilink
    arrow-up
    1
    ·
    7 months ago

    I looked at it and there’s a lot of them!

    I see things like adding dependencies but I would add the dependency along with the code that’s using it so I have that context. Is the Gitmoji way to break your commits up so that it matches a single category?

    • jaemo@sh.itjust.works
      link
      fedilink
      arrow-up
      2
      ·
      7 months ago

      Yes, that is another benefit, once you start getting muscle memory with the library. You start to parcel things by context a bit more. It’s upped my habit of discrete commit-by-hunks, which also serves as a nice self-review of the work.

      • Deebster@programming.dev
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        7 months ago

        I don’t see that as a benefit tbh - if I have a dependency, I want to see why it’s there as part of the commit. I’m imagining running blame on Cargo.toml and seeing “Add feature x” vs “Add dependency”. I guess the idea is it’s “➕ Add dep y for feature x” but I’d still rather be able to see the related code in the same commit instead of having to find the useful commit in the log.

        I suppose you could squash them together later, but then why bother splitting it out in the first place?

        I see that some use a subset of Gitmoji and that does make sense to me - after all, you wouldn’t use all of them in every project anyway, e.g. 🏷️ types is only relevant for a few languages.