TEST: Test linter

[daniel-falk]

Summary by CodeRabbit

• Tests
  • Added simple shell scripts and a sample JSON fixture to support internal testing and validation. These additions do not alter app behavior or public interfaces. No runtime impact.
• Chores
  • Introduced lightweight scaffolding assets to aid development processes. No performance, UI, or API changes; end-users are unaffected. Safe to deploy with no configuration changes.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Adds three new files: test.json containing { "test": 1 }, test.sh containing three lines (A, B, C), and test2.sh containing a single line bcd. No modifications to existing files, no control flow or public API changes.

Changes

Cohort / File(s)	Summary of Changes
New files test.json, test.sh, test2.sh	Added test.json with { "test": 1 }; added test.sh with three lines (A, B, C); added test2.sh with a single line bcd.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between b92bade and c7b0dd9.

📒 Files selected for processing (3)

• test.json (1 hunks)
• test.sh (1 hunks)
• test2.sh (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch test-linter

---

🪧 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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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.

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.

[github-actions]

🎨 Code Formatting Required

Prettier Formatting Issues

Some files need to be formatted with Prettier (JSON, YAML, Markdown).

Files that need prettier formatting:

• test.json

To fix prettier issues:

npx prettier@3.6.0 --write "**/*.{json,yml,yaml,md}" ".github/**/*.{json,yml,yaml,md}" ".*.{yml,yaml,json,md}" --ignore-unknown

Trailing Whitespace Issues

Some files have trailing whitespace (spaces/tabs at end of lines).

Files with trailing whitespace:

• ./test.sh
• ./test2.sh

To fix: Remove the trailing spaces/tabs at the end of lines in your favorite editor.

After fixing:

1. Commit and push the changes
2. The formatting check will automatically pass

[github-actions]

🎨 Code Formatting Required

Trailing Whitespace Issues

Some files have trailing whitespace (spaces/tabs at end of lines).

Files with trailing whitespace:

• ./test.sh
• ./test2.sh

To fix: Remove the trailing spaces/tabs at the end of lines in your favorite editor.

After fixing:

1. Commit and push the changes
2. The formatting check will automatically pass

[github-actions]

🎨 Code Formatting Required

Trailing Whitespace Issues

Some files have trailing whitespace (spaces/tabs at end of lines).

Files with trailing whitespace:

• ./test.sh

To fix: Remove the trailing spaces/tabs at the end of lines in your favorite editor.

After fixing:

1. Commit and push the changes
2. The formatting check will automatically pass