Added Super-Linter

[ulises-jeremias]

Summary by CodeRabbit

• New Feature: We've added a new quality assurance measure to our development process. This includes a "super-linter" that automatically checks our code for any issues whenever changes are made. This ensures the code you interact with is of the highest quality and reduces the likelihood of encountering bugs or errors.

[coderabbitai]

Walkthrough

The recent changes introduce a new job in the GitHub workflow that enhances code quality checks. The "super-linter" job, triggered on both push and pull request events, uses the Super-Linter tool to scrutinize the code, ensuring adherence to best practices.

Changes

File	Summary
.github/workflows/lint.yml	Added a new job "super-linter" that runs on push and pull request events. The job uses Super-Linter for code checks. The existing "docs" job remains unchanged.

🐇🎉

Code is the garden where ideas grow,

With each commit, we sow a new row.

Super-Linter's watchful eyes,

Help our garden of code to rise.

So here's to changes, big and small,

May our codebase stand tall! 🎉🐇

---

Tips

Chat with CodeRabbit Bot (@coderabbitai)

• If you reply to a review comment from CodeRabbit, the bot will automatically respond.
• To engage with CodeRabbit bot directly around the specific lines of code in the PR, mention @coderabbitai in your review comment
• Note: Review comments are made on code diffs or files, not on the PR overview.
• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai help to get help.
• @coderabbitai resolve to resolve all the CodeRabbit review comments.

Note: For conversation with the bot, please use the review comments on code diffs or files.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.json

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between c806a5a and c2e3a4b.

Files selected for processing (1)

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

Additional comments: 3

.github/workflows/lint.yml (3)

• 2-10: The workflow is triggered on both push and pull request events for the "main" branch. Ensure that this is the desired behavior. If you want to run the linter on all branches, you can remove the branches specification.

• 14-28: The "super-linter" job is well defined. It checks out the code and runs the Super-Linter on it. The environment variables are correctly set. Make sure that the GITHUB_TOKEN secret is properly set in your repository settings.

• 29-31: The "docs" job is not affected by the changes in this pull request. However, it seems to be incomplete as the steps to execute the job are not included in the hunk. Please verify if the job is correctly defined in the full file.

The remaining code is not part of the hunk and cannot be reviewed.