#68 - super-linter implementation

[AgusCastro]

What's this PR do?

This PR solves #68

Summary by CodeRabbit

Chores:

• Implemented a new GitHub Actions workflow named "Lint Code Base". This workflow will automatically check the code for any inconsistencies or errors whenever changes are pushed or a pull request is made on the main branch. This ensures that our codebase remains clean and error-free, improving the overall quality of our software.

[coderabbitai]

Walkthrough

The changes introduce a new GitHub Actions workflow, "Lint Code Base", which is triggered 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.

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. Environment variables are set for the action.

Poem

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

A rabbit hops, code in sight, making sure it's just right. 🐇💻

With a linting spell, and a GitHub bell, 🔔✨

The code's now neat, and oh so swell! 🎉🥳

So let's celebrate, with a carrot cake, 🥕🍰

For the great code journey, we continue to make! 🚀🌌

Validation with GitHub issue(Beta)

Assessment of the PR changes against GitHub Issue

Aspect	Aligns with the linked issue	Explanation
Workflow file creation	☑️	The pull request includes the creation of a GitHub Actions workflow file, which aligns with the issue's requirement to update the .github/workflows configuration file.
Use of "super-linter"	☑️	The pull request uses the "super-linter" action for linting, which is the tool proposed in the issue.
Event triggers	☑️	The workflow file is set to run on push and pull_request events on the main branch, which is a common practice and doesn't contradict the issue.
Environment variables	☑️	The environment variables are set in the workflow file, including VALIDATE_ALL_CODEBASE, DEFAULT_BRANCH, and GITHUB_TOKEN. This aligns with the issue's requirement for easy configuration.
Linting of all relevant languages	❓	The pull request doesn't specify if the "super-linter" is configured to lint all relevant languages as required by the issue. This needs to be confirmed.

 </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 187b798 and 42e5ead.

Files selected for processing (1)

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

Additional comments: 1

.github/workflows/lint.yml (1)

• 1-31: The workflow file looks good. It correctly sets up a GitHub Actions workflow to lint the codebase on push and pull_request events on the main branch. The use of the super-linter action with the appropriate environment variables is a good practice. The permissions are also correctly set for the workflow.