Discuss use of keywords for linking issues that are closed by commits

[javier-godoy]

We need to discuss the use of keywords for linking issues that are closed by commits, and confirm whether Flowing Code Commit Message Guidelines / 1.0.0-rc.8 aligns with our current practice.

1. According to the Guidelines, the commit message footer to be used for linking the issue that is closed by the commit is Close #. GitHub supports other keywords (closes, closed, fix, fixes, fixed, resolve, resolves and resolved). In some cases other keywords have been used. It seems we don't have a strong feeling about this point (and requesting changes in a PR just because they used the "wrong" footer seems too pedantic)

2. GitHub also allows the keyword to be followed by colons (e.g. Closes: #) while the Guidelines do not allow that syntax.

3. Both GitHub and the Guidelines specify that the keywords are case-insensitive, while common practice seems to be capitalizing only the first letter.

[ngonzalezpazFC]

In my opinion as the closing keyword is required only to close GitHub issues, the most appropriate is Close #X. Also, this word is consistent with the required subject tense (imperative present).
Regarding fix, fixes or fixed keywords could be redundant in a fix: commit type.

[paodb]

I agree that using Close # as already specified is the way to go. It clearly communicates the intent, the commit is directly responsible for closing the referenced issue. We shouldn't change our guideline, we should make sure it is used as expected.