Minor changes.

[ypriverol]

Summary by CodeRabbit

• New Features

  • Introduced a new configuration file for enhanced code quality checks.

• Documentation

  • Updated the README to reflect the new build status and code coverage badge links.

• Chores

  • Changed the environment name in the configuration file and removed the pyarrow dependency from relevant files.

[coderabbitai]

Warning

Rate limit exceeded

@ypriverol has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 6 minutes and 3 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between ee98b08 and f328b7d.

Walkthrough

The changes in this pull request introduce a new configuration file .codacy.yml for setting up code quality checks using eslint and pylint, while excluding test files. The README.md file is updated to reflect a change in the CI badge from Travis CI to GitHub Actions and updates the code coverage badge URL. Additionally, the environment.yml file changes the environment name from quantmsutils to quantms-rescoring and removes the pyarrow dependency. The recipe/meta.yaml file also removes the pyarrow dependency from its runtime requirements.

Changes

File	Change Summary
.codacy.yml	New configuration file added for eslint and pylint, excluding tests directory from analysis.
README.md	Updated build status badge from Travis CI to GitHub Actions and changed code coverage badge URL.
environment.yml	Changed environment name from quantmsutils to quantms-rescoring and removed pyarrow from dependencies.
recipe/meta.yaml	Removed pyarrow from the run section under requirements.

Possibly related PRs

• second biggest commit. #1: The changes in the README.md file include a project name update from "quantms-ms2rescore" to "quantms-rescoring," which is directly related to the overall project context of the main PR.

🐇 In the code we hop and play,
New badges shine, bright as day!
With linting tools to guide our way,
Dependencies trimmed, we’re here to stay.
In the garden of code, we’ll leap and bound,
For quality checks, our joy is found! 🌼

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • 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 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 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 using 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.

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.

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 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 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.

[coderabbitai]

Actionable comments posted: 2

🧹 Outside diff range and nitpick comments (1)

.codacy.yml (1)

16-17: Fix YAML formatting issues

There are two formatting issues in this section:

1. Inconsistent indentation (4 spaces instead of 2)
2. Missing newline at end of file

Apply this diff to fix the formatting:

 exclude_paths:
-    - 'tests/**'
+  - 'tests/**'
+

🧰 Tools

🪛 yamllint (1.35.1)

[warning] 17-17: wrong indentation: expected 2 but found 4

(indentation)

---

[error] 17-17: no new line character at the end of file

(new-line-at-end-of-file)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between f74c269 and ee98b08.

📒 Files selected for processing (4)

• .codacy.yml (1 hunks)
• README.md (1 hunks)
• environment.yml (1 hunks)
• recipe/meta.yaml (0 hunks)

💤 Files with no reviewable changes (1)

• recipe/meta.yaml

✅ Files skipped from review due to trivial changes (2)

• environment.yml
• README.md

🧰 Additional context used

🪛 yamllint (1.35.1)

.codacy.yml

[warning] 17-17: wrong indentation: expected 2 but found 4

(indentation)

---

[error] 17-17: no new line character at the end of file

(new-line-at-end-of-file)

🔇 Additional comments (1)

.codacy.yml (1)

1-6: LGTM: Engine configuration looks good

The basic engine configuration for eslint and pylint is correctly set up.