fix: enforce a lower case letter at the beginning of the summary content

[aeyoll]

No description provided.

[cocogitto-bot]

✔️ f9a6fc6 - Conventional commits check succeeded.

[oknozor]

Hey @aeyoll I am a bit confused, is this mentioned in the conventional commit spec ?

[aeyoll]

Hey @oknozor,
It's not per se in the conventional commit spec, but it's present in the angular commit message spec and tools like commitlint is enforcing it by default.

I understand that it can be out of scope for this project if its not described in the spec.

However, maybe it could be a configurable option in the parser?

(My goal behind all this is to ditch commitlint and replace it with cog verify in all my repositories, where the "lowercase" rule is already in place)

Thanks a lot

[oknozor]

Hey @aeyoll,

Thanks for the suggestion but I cannot merge this as is.
Adding angular commit to cocogitto as an additional layer on top of the conventional commit spec seems ok to me.
That said, breaking the current implementation ( which is conform to the spec ) is not an option here.

However, maybe it could be a configurable option in the parser?

This is the way to go. Ideally we could expose a parser builder which would allow to add more parsing options without breaking the public API again.

Also adding the lowercase rule only is not ideal. I'd rather have the angular commit spec implemented all at once.

Regarding the implementation I think the pest grammar file for the conventional commit spec should be left untouched.
It describes the conventional commit parser and should not be mixed with angular commit.
Their are few additional rules a second pass on the already parser conventional commit would do. I am not even sure
pest is needed here.

Once we have this in the parser I would be trivial to add an angular commit flag/config to the cli.

Let me know if you want to work on it.

[aeyoll]

Thanks for the feedback, I totally understand that you can't merge it.

Also adding the lowercase rule only is not ideal. I'd rather have the angular commit spec implemented all at once.

The Angular spec is actually not that different from conventional commit spec, I think it only adds this lower case rule, plus a max length of 100 of every line of the message.

Ideally we could expose a parser builder which would allow to add more parsing options without breaking the public API again.
Their are few additional rules a second pass on the already parser conventional commit would do. I am not even sure
pest is needed here.

It would be the easiest way, but it adds another layer of verification on top of pest, I'm not sure if it's the most elegant solution. We could have multiple grammar files, but they would have a lot of similarities, which is not ideal either. Too bad pest doesn't allow to share rules between multiple grammars.