add .gitmessage template and git hook

[geyslan]

1. Explain what the PR does

25e4800 chore(git): add .gitmessage template and git hook _{(2023/jun/28) Geyslan Gregório <geyslan@gmail.com>}

To use this template, after a fresh clone, create a symlink:
  ln -s ../../git-hooks/prepare-commit-msg .git/hooks/prepare-commit-msg

2. Explain how to test it

git commit shows default commit msg appended with .gitmessage template.

3. Other comments

[rafaeldtinoco]

I personally don't like having git hooks and other attempts we had in the past to do such a long test as a "template" failed. I'll let @yanivagman to decide this one.

[geyslan]

I personally don't like having git hooks and other attempts we had in the past to do such a long test as a "template" failed. I'll let @yanivagman to decide this one.

I understand. My proposal is to let the template available but don't force the contributor to use it (considering that it's just a commented template for guidance), so we could add a doc about its existence.

[josedonizetti]

I also don't like git hooks, would prefer we validate it on our CI instead, i think it will more useful, if the templated is not enforced, in my view most people won't use it and it will get obsolete.

[geyslan]

I don't think we should enforce formatting (even in CI), just suggest it. I'm going to convert this into a contribution doc (suggesting) the formatting. WDYT?

[rafaeldtinoco]

in my view most people won't use it and it will get obsolete.

+1 on that.

I'm going to convert this into a contribution doc (suggesting) the formatting. WDYT?

I believe we should ENFORCE the git log subject formatting to this:

# <type>(scope): <description>
#
# (optional body)
#
# (optional footer(s))
#
# Type can be:
#	feat:     A new feature
#	fix:      A bug fix
#	docs:     Documentation changes
#	style:    Code style changes (formatting, indentation, etc.)
#	refactor: Code restructuring that neither fixes a bug nor adds a feature
#	perf:     Performance improvements
#	test:     Adding or modifying tests
#	build:    Changes to the build system or dependencies
#	chore:    Other changes that don't modify src or test files
#	revert:   Reverts a previous commit

and forget about the rest. We should enforce as a PR check IMO.

[geyslan]

Ok, so closing this PR.