ci: linter configuration

[matous-volf]

Summary by CodeRabbit

• New Features
  • Introduced new environment variables for enhanced control over linting processes: VALIDATE_JAVASCRIPT_PRETTIER, VALIDATE_JAVASCRIPT_STANDARD, VALIDATE_RUST_2015, VALIDATE_RUST_2018, and VALIDATE_SQLFLUFF, all defaulting to false.
• Improvements
  • Enhanced flexibility in the CI/CD pipeline, allowing developers to customize which validation tools are active for better code quality management.

[coderabbitai[bot]]

Walkthrough

The recent updates to the GitHub Actions workflow configuration enhance the flexibility of the linting process by introducing five new environment variables. These variables allow developers to selectively enable or disable validation tools for JavaScript and Rust code, as well as SQL formatting, making the continuous integration process more customizable. This change aims to improve code quality and adherence to standards by providing better control over the linting practices employed in the CI/CD pipeline.

Changes

Files	Change Summary
.github/workflows/lint.yml	Added five new environment variables (VALIDATE_JAVASCRIPT_PRETTIER, VALIDATE_JAVASCRIPT_STANDARD, VALIDATE_RUST_2015, VALIDATE_RUST_2018, VALIDATE_SQLFLUFF), all set to false, allowing for more granular control over linting options.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant CI/CD Pipeline
    participant Linting Tools

    Developer->>CI/CD Pipeline: Commit changes
    CI/CD Pipeline->>Linting Tools: Run linting based on environment variables
    Linting Tools-->>CI/CD Pipeline: Return linting results
    CI/CD Pipeline-->>Developer: Notify build status

---

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `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 generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@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 as 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. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.