Allow `patch` as an alternative/alias to `fix`
lzambarda opened this issue · 1 comments
While reading v1.0.0 I noticed the following:
fix: a commit of the type fix patches a bug in your codebase (this correlates with PATCH in Semantic Versioning).
This is a good description because as developers we patch things more often than we fix them (a level of uncertainty in having fixed certain bugs is not uncommon).
Therefore I would argue that patch
should be allowed as an alternative to fix
if not even used as a replacement.
The challenge with aliasing the foundational types (fix
and feat
), is that there's a significant ecosystem of tooling that exists already for conventional commits.
Perhaps we could instead provide more direction in the non-normative text, about how to use alternative types? If in your project you would prefer to use patch
to fix
, this is perfectly reasonable if you can get your toolchain setup to handle it -- I'm hesitant to overhaul the normative text of the spec to handle this behaviour...
I think I feel the same way regarding using feature
, rather than feat
, which I used to be supportive of. This spec has been in the wild for a few years now, there's a healthy amount of tooling around it, and I think it's serving its purpose well.
This is just one opinion though!