delta/gitlab/gitlab-ce.git/danger/commit_messages, branch docs-instance_level_clusters

Run rubocop -a on CE files

2019-05-05T10:24:28+00:00

Resolve "Fix danger commit messages check"

2019-02-22T11:56:45+00:00

Refactor commit_messages#lint_commit

2019-02-20T13:25:12+00:00

This introduces additional method for linting,
to reduce the complexity of `lint_commits`.

Ignore revert commits

2019-02-19T14:05:45+00:00

Fix Danger commit message errors

2019-01-11T22:22:10+00:00

Shorten danger 50 char commit warning

2019-01-11T13:33:02+00:00

- Also pulls URLs into vars

Only detect short refs followed by \b in Danger

2019-01-08T15:37:06+00:00

Signed-off-by: Rémy Coutable

Clarify messaging on what fails for too many failed lines

2018-12-17T06:42:59+00:00

Relax the subject line requirements for commits

2018-09-19T13:27:50+00:00

This changes the hard limit of 50 to a soft limit of 50, with the new
hard limit being 72 characters. This gives people a bit more space,
while still (hopefully) guiding them towards subject lines that are
roughly 50 characters long.

Fixes https://gitlab.com/gitlab-org/release/framework/issues/16

Improve Emoji detection in commit messages

2018-09-18T14:22:29+00:00

This changes our Danger integration so that it is smarter about
detecting GitLab emoji in commit messages. This is done using a two step
process:

1. We use the old regular expression to determine if a commit message
   _might_ include an emoji.

2. If this regular expression matches, we then check for all existing
   emoji names in the commit message. This might be a wee bit expensive,
   but because we couple it with the previous step it should be rarely
   executed.

This ensures we don't trigger an error when a commit message includes
text such as `:foo:bar:`, which is not a valid Emoji.

Fixes https://gitlab.com/gitlab-org/release/framework/issues/15