

Assuming that works on the Fediverse.
It’s up to each instance. The instance of the viewer, not yours. So from your perspective, if it’s a guarantee you want, then no, it doesn’t work on the fediverse.
I’m a #SoftwareDeveloper from #Switzerland. My languages are #Java, #CSharp, #Javascript, German, English, and #SwissGerman. I’m in the process of #LearningJapanese.
I like to make custom #UserScripts and #UserStyles to personalize my experience on the web. In terms of #Gaming, currently I’m mainly interested in #VintageStory and #HonkaiStarRail. I’m a big fan of #Modding.
I also watch #Anime and read #Manga.
#fedi22 (for fediverse.info)


Assuming that works on the Fediverse.
It’s up to each instance. The instance of the viewer, not yours. So from your perspective, if it’s a guarantee you want, then no, it doesn’t work on the fediverse.


And fix and feat aren’t supposed to be pointless and stupid if done properly.


It sounds to me like you’re just dealing with people who write bad commit messages.
Or commits in general if you’re dealing with “feats” containing bug fixes.
It doesn’t sound to me like your core problem is with conventional commits themselves, but rather with how they’re done in your experience.
Inconsistency and unclear meaning does make it just some random noise, but that’s not how the standard is meant, that’s just people using it irresponsibly.
“chore” is just too cute by half. I know “Version bump: 1.2.3” is just a version bump - I don’t need you to whine about it being a chore.
Worth noting that only fix and feat are actual types defined by the official spec. chore is only listed as an example of what custom types you could use. So as long as you make sure the rest of the team is on the same page, you can also use a different noun like bump or version instead.
“feats” can have refactors and bug fixes. fix can add new features. Devs are horribly bad at separating out these types of changes neatly when making commits.
Actually looking through Conventional Commit’s page again, I also found this on-topic Q&A question:
What do I do if the commit conforms to more than one of the commit types?
Go back and make multiple commits whenever possible. Part of the benefit of Conventional Commits is its ability to drive us to make more organized commits and PRs.
When both a bug fix and a feat are in the same commit, the answer isn’t to use one or the other, but to simplify the commit. I personally see more valid overlap with refactor (which isn’t an official type), but with these two, it’s inexcusable imo.


It’s 3-5 letters you slap at the start of your succinct change description. I don’t see how it’s that big of a deal to get this upset about.


Not going to use this one either, but I wish I could use LibreOffice.
It’s really laggy for me on Windows. Particulary when interacting with the window, moving or resizing it. It’s not smooth at all. As someone who uses everything windowed and moves windows around all the time, I tried using it, but it’s unusable for me imo.


How do you identify a “slop kiddie”? It’s not like LLM users identify themselves as such.
You’ll have to judge by their code, at which point you’re already not ignoring them at all.
Reminds me of Mycelium, a federated AI project which died last year.