GitLab rather explicitly state that they ignore most of a Code Climate report, and they only use the four following fields: fingerprint, location.path, location.lines.begin and location.description.
To me it feels that the description is what should be used to put issue.getMessage(). Moreover, the Code Climate doc shows examples of check_name that really are the name of the rule being used to produce an output, and not a human-readable description of how this rule, in this specific instance, doesn't work.
So, since GitLab won't show check_name, and since description is a better match for a Sonar issue message than check_name, I'm submitting this request.
Hi,
GitLab rather explicitly state that they ignore most of a Code Climate report, and they only use the four following fields: fingerprint, location.path, location.lines.begin and location.description.
To me it feels that the
description
is what should be used to put issue.getMessage(). Moreover, the Code Climate doc shows examples ofcheck_name
that really are the name of the rule being used to produce an output, and not a human-readable description of how this rule, in this specific instance, doesn't work.So, since GitLab won't show
check_name
, and sincedescription
is a better match for a Sonar issue message thancheck_name
, I'm submitting this request.