Commit message standards?

Question

git

According to this commit standard .
There is a list of types of commits
But I still can't decide which one is more suitable for the following task:

Let's say there is a modal, or a link that opens the modal. The task is simple to temporarily hide it, because now it is no longer needed, but maybe someday it will return, for now we just hide the link and the modal.
Or block access to this page for everyone, also roughly speaking hide. We'll open it up later when the time comes.

What type of commit is best for this task? I'm suspicious of a chore. What
would you choose if you followed the commit message standard?

Answer 1

It's definitely not a `chore`, as it refers to production code.
`chore` is anything around the code, unless a narrower type is provided.
Linters (if you don't use `style`), CI setup (if you don't use `ci`), all sorts of additional tooling like `husky` or `lint-staged`, minor dependency updates, and so on.
Your list of commit types by reference is just one of the popular conventions between developers (I mean, there are others).
Moreover, it can be easily expanded with other types, if you need it, no one will throw stones at you.
If you want to strictly follow, then your edit is either `fix` or `feat`.
But for myself and for the team, I introduced an additional type `temp` (from `temporal`) just for such a sense of change.
When "the time comes", you can simply search for that type to quickly find it and do a `revert`.
Also expanded with `nvm` type (from `nevermind`) for fixes like "forgot a space in readme" and other minor things.
Although formally it can be expressed through `docs`, `refactor`, `style` or `fix`, the presence of such commits in the changelog is neither hot nor cold for anyone, so they are simply not included in it.
Expand the configuration to what you need and your changes, and everything will be fine.
* However, experience and common sense tell us that the fewer types there are, the less chance of error and the greater the chance that they will be used. Without fanaticism, in short: