Draft status and conventional commit warning
Purpose
In Pajamas we require use of conventional commits, which impact how an MR should be titled. As part of the GitLab process we set an MR as a draft to indicate it's not ready to be merged. A draft MR prefixes the title with 'Draft:', but this in turn causes Danger Bot to warn a user that "The semantic commit type Draft
is not a well-known semantic commit type."
Conventional commits are frequently mentioned as part of the learning curve for contributing to Pajamas. When the error seems to suggest a conflict between a GitLab feature/process and the conventional commit standards it adds unnecessary friction.
Proposal
Could we either…
- A - Remove the warning altogether.
- B - Update the warning message to note that "'Draft:' in the title will prevent the conventional commits job from passing."
The goal is to inform a user that an MR in draft status won't pass conventional commits based on that alone (there may be other reasons it doesn't pass), but that it's ok to keep it in draft.