Use GitHub deprecated formatter for stylelint

[tagliala]

This formatter has been deprecated, but the suggested alternative does
not work and seems unmaintained

Ref:

• Deprecate built-in github formatter xt0rted/stylelint-actions-formatters#187
• New version xt0rted/stylelint-problem-matcher#461
• Trying to add annotations to stylelint without success xt0rted/stylelint-problem-matcher#592

Summary by CodeRabbit

• Chores
  • Updated the GitHub Actions workflow for improved Stylelint output compatibility with GitHub.
  • Corrected YAML formatting for the Stylelint step.

[coderabbitai]

Walkthrough

The pull request modifies the GitHub Actions workflow located in .github/workflows/lint.yml. It introduces a --formatter=github option to the Stylelint job, changing the output format to be compatible with GitHub's interface. Additionally, the indentation of the run command for the Stylelint step has been corrected to ensure proper YAML formatting. Other linting jobs remain unchanged.

Changes

File	Change Summary
.github/workflows/lint.yml	Added --formatter=github to Stylelint job; corrected indentation.

Possibly related PRs

• Optimize CI by conditionally running lint jobs #980: The changes in this PR also involve modifications to the .github/workflows/lint.yml file, specifically related to the Stylelint job, which is directly relevant to the changes made in the main PR regarding the output format and YAML formatting corrections.

Poem

In the garden of code, we hop and play,
With Stylelint's whispers, we brighten the day.
A formatter added, all neat and aligned,
In YAML’s embrace, our outputs refined.
So let’s dance through the branches, with joy we proclaim,
For each little change, we celebrate the game! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between e0556bf and 5c28a0f.

📒 Files selected for processing (1)

• .github/workflows/lint.yml (1 hunks)

🧰 Additional context used

🔇 Additional comments (1)

.github/workflows/lint.yml (1)

113-113: LGTM: Use of GitHub deprecated formatter is justified.

The addition of --formatter=github to the stylelint command is appropriate given the context provided in the PR description. This change aligns with the PR objectives and addresses the need for GitHub-compatible output.

While this solution is currently the best option due to issues with the suggested alternative, it's advisable to monitor the situation for future updates or new alternatives. Consider adding a TODO comment or creating an issue to revisit this in the future.

To verify the impact and usage of this formatter, you can run the following script:

This script will help identify any other instances where stylelint formatters are used, as well as any existing TODO comments or discussions related to this topic.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coveralls]

Pull Request Test Coverage Report for Build 11314292595

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 11240297348:	0.0%
Covered Lines:	19
Relevant Lines:	19

---

💛 - Coveralls