How will commits that don't match any of the regexes in commit_parsers be grouped?

If they are conventional, they will appear in their own section. For example, foo(bar): xyz will be:

### Foo
- (bar): xyz

If they are not conventional, they will be skipped. We can potentially set up git-cliff to utilize unconventional commits as well but the most of the codebase seems to be using conventional commits so I'd say there is no need for that. Conventional commits gud.

How is it determined which part of the codebase the commit belongs too (e.g. (gateway) <commit message>?

From the scope of the commit message, e.g. feat(gateway): <commit message>

Alright, so we'll have to make sure we modify names of commits when we squash them (if needed). Would be good to have non-matching ones get thrown into Misc. just in case.

Done in b3bd557

Perfect, thanks!