You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am aware that php-cs-fixer do not have specific severity for each issue but we could generate a default one to all issues for the gitlab format (info or minor) ?
This way, Gitlab will correclty show Code Quality panel in merge request using gitlab format of php cs fixer.
The text was updated successfully, but these errors were encountered:
Version
Bug report
I do not find a way to make Gitlab merge request show Code quality report from php cs fixer using
gitlab
format.Code snippet that reproduces the problem
I simplificated my current Gitlab job to be more understanding but didn't had time to make it working, sorry.
Test case
Observed result
Job has failed (good) but no quality report is available in Gitlab merge request (not good) :
Expected result
Code quality should have been displayed in Gitlab merge request interface.
Analyze
severity
field : https://github.com/FriendsOfPHP/PHP-CS-Fixer/blob/00096f01266da9160dadced3421df34369522a86/src/Console/Report/FixReport/GitlabReporter.php#L43-L52severity
field seems to be mandatory by Gitlab to be correctly displayed in Gitlab interface : https://docs.gitlab.com/ee/user/project/merge_requests/code_quality.html#implementing-a-custom-toolseverity
field but others fields required by specification are not used by Gitlab. Therefore, Gitlab do not follow strictly Code Climate Engine Specification : https://github.com/codeclimate/platform/blob/master/spec/analyzers/SPEC.md#issuesExamples
It wasn't recognized by Gitlab.
This time it worked well,
Fix ?
I am aware that php-cs-fixer do not have specific severity for each issue but we could generate a default one to all issues for the gitlab format (
info
orminor
) ?This way, Gitlab will correclty show Code Quality panel in merge request using gitlab format of php cs fixer.
The text was updated successfully, but these errors were encountered: