- Issue created by @fjgarlin
- Status changed to Active
about 1 year ago 1:21pm 13 September 2023 - First commit to issue fork.
- Status changed to Needs review
about 1 year ago 4:23pm 13 September 2023 - last update
about 1 year ago 30,150 pass - @longwave opened merge request.
- 🇬🇧United Kingdom longwave UK
As an alternative I also found https://gitlab.com/leon0399/stylelint-formatter-gitlab - is it better to use a native GitLab format instead of JUnit?
- 🇬🇧United Kingdom longwave UK
Stylelint report shows up at https://git.drupalcode.org/project/drupal/-/pipelines/19663/test_report
- Status changed to RTBC
about 1 year ago 3:41pm 15 September 2023 - 🇺🇸United States smustgrave
Change itself looks good and all green. Will let committer decide if we need a follow up for the removal of the one package.
- last update
about 1 year ago 30,158 pass - Status changed to Needs review
about 1 year ago 7:23pm 15 September 2023 - 🇬🇧United Kingdom catch
I think we should decide whether we're going to use https://gitlab.com/leon0399/stylelint-formatter-gitlab or not here, or at least explicitly decide to defer it to a follow-up if not.
- 🇬🇧United Kingdom longwave UK
I think this should be closed as duplicate of ✨ Integrate codequality reports into Gitlab RTBC as that has a good argument for switching the package and makes more changes along the same lines.
- Status changed to Closed: duplicate
about 1 year ago 9:20pm 15 September 2023 - 🇬🇧United Kingdom catch
Makes sense, marking duplicate and let's continue over there.