Documentation | Clarify commit message header "tags" (#132)

[Gedare Bloom (@gedare)]

Gedare Bloom created an issue: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/issues/132



## Summary
<!--
Please provide as much information as possible such as error messages or attaching logs
-->
I'd like to make the commit messages a little more strict in terms of the "tag" that a commit message starts with. 

I propose that we use a two-part tag, the first part being the first subdirectory within rtems.git (or rtems-docs.git, and other repos?) and the second part being the directory containing the common set of changes.

This would allow us to also start to provide stronger CI checks on it and make it more clear what we expect
As a counter example, this commit message would not be compliant: https://gitlab.rtems.org/rtems/rtos/rtems/-/commit/b8d245499ef9bca5e6f6ac39f48adebb2c989b36
instead of using
`testsuites/sptests/spcache01/init.c: Address -Wclobbered warning`
it would be:
`testsuites/spcache01: Address -Wclobbered warning`
similarly, this one would need an additional directory specified: https://gitlab.rtems.org/rtems/rtos/rtems/-/commit/8ab6a256d3de3c4988cf1f4563cbe06f9676517f
instead of
`ignore: Add contrib`
it would be
`.gitlab/ignore: Add contrib`


## Steps to reproduce


<!-- Pre-set options
- milestone
-->

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/issues/132
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260127/f92cb9c8/attachment.htm>