Skip to content

danger: Make two commit guidelines warnings instead of errors

Rémy Coutable requested to merge relax-two-commit-guidelines into master

What does this MR do?

  1. In some cases, it doesn't make sense to enforce a commit body when the changes changes many lines/files, but are very trivial (e.g. mass replacemnt/removal).
  2. In some cases (e.g. when including stacktrace), it doesn't make sense to wrap lines, making it impossible to satisfy the "details line may not be longer than 72 characters".

This was reported via Slack recently and I think it makes sense to make these rules warnings instead of errors.

Edited by Rémy Coutable

Merge request reports