#54 - Super-linter implementation

[AgusCastro]

What's this PR do?

This PR solves #54

[coderabbitai]

Walkthrough

The changes introduced a new GitHub Actions workflow named "Lint Code Base". This workflow is triggered on push and pull_request events on the main branch. It checks out the code, fetches the full git history, and uses the "super-linter" action to lint the code base, with specific environment configurations.

Changes

File	Summary
.github/workflows/lint.yml	Added a GitHub Actions workflow "Lint Code Base" that runs on push and pull_request events on the main branch. The workflow checks out the code, fetches the full git history, and uses the "super-linter" action to lint the code base with specific environment configurations.

Poem

🎃 On this Halloween night, under the moon's bright light, 🌕

A rabbit hopped and wrote some code, making everything right. 🐇💻

With a linting workflow in place, no error can hide its face, 👻

Ensuring our code is neat, running at a steady pace. 🏃‍♀️💨

So let's celebrate this feat, with some candy, oh so sweet! 🍬🎉

Happy coding to all, and to all a good-night! 🌙✨

Validation with GitHub issue(Beta)

Assessment of the PR changes against GitHub Issue

Aspect	Aligns with the linked issue	Explanation
Use of "super-linter"	☑️	The pull request uses the "super-linter" action for linting, which aligns with the issue's requirement to use "super-linter".
Configuration of "super-linter"	☑️	The pull request configures the "super-linter" with environment variables, which aligns with the issue's requirement to configure "super-linter".
Creation/Update of .github/workflows configuration file	☑️	The pull request adds a new workflow file in .github/workflows, which aligns with the issue's requirement to create or update the .github/workflows configuration file.
Linting process testing	❌	The pull request does not mention any testing of the linting process, which is a requirement in the issue.
Linting coverage for all relevant languages	❌	The pull request does not specify if the linting process covers all relevant languages, which is a requirement in the issue.

 </details><!-- This is an auto-generated comment: raw summary by coderabbit.ai -->

---

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 29b5253 and e441ad5.

Files selected for processing (1)

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

Additional comments: 1

.github/workflows/lint.yml (1)

• 1-31: The workflow configuration looks good. It's set to run on both push and pull_request events on the main branch. The super-linter is correctly configured with the necessary environment variables. Ensure that the GitHub token has the necessary permissions to run this workflow.