[pre-commit.ci] pre-commit autoupdate
updates:
- github.com/pre-commit/pre-commit-hooks: v4.6.0 → v5.0.0
- github.com/psf/black: 24.4.2 → 24.10.0
- github.com/astral-sh/ruff-pre-commit: v0.5.4 → v0.6.9
Summary by CodeRabbit
-
New Features
- Updated the code formatter to enhance formatting consistency, performance, and compliance with the latest Python syntax.
- Upgraded the linter to improve linting capabilities and overall code quality.
-
Improvements
- Enhanced the organization of import statements in the notebook for better readability and maintainability.
- Reformatted code blocks in the notebook to improve clarity and ease of understanding.
- Standardized parameter order in export function calls, improving readability and maintainability across scripts.
[!IMPORTANT]
Review skipped
Bot user detected.
To trigger a single review, invoke the
@coderabbitai reviewcommand.You can disable this status message by setting the
reviews.review_statustofalsein the CodeRabbit configuration file.
Walkthrough
The updates involve upgrading the versions of the black code formatter from 24.4.2 to 24.8.0 and the ruff linter from v0.5.4 to v0.6.1 in the .pre-commit-config.yaml file. Additionally, modifications were made to an IPython notebook, focusing on reordering imports and enhancing the readability of a specific code block. Changes were also made to parameter orders in function calls across multiple Python files.
Changes
| Files | Change Summary |
|---|---|
.pre-commit-config.yaml |
Updated black from 24.4.2 to 24.8.0; updated ruff from v0.5.4 to v0.6.1. |
examples/ipynb/notebook_showcase_k3d.ipynb |
Reordered import statements and reformatted the creation of the empty_torus object for readability. |
examples/export_meshio.py |
Rearranged parameters in calls to gus.io.meshio.export to place export path as the first argument. |
examples/mixd_to_nutils.py |
Changed argument order in calls to gus.io.mixd.export and gus.io.nutils.export, placing filepath first. |
Poem
🐇 In the code garden, tools refine,
Black and Ruff, oh how they shine!
With versions fresh, they prance and play,
Ensuring clean code, come what may.
Hooray for upgrades, let us cheer,
For better coding year by year! 🎉
🪧 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
@coderabbitaiin 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
@coderabbitaiin 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 pauseto pause the reviews on a PR. -
@coderabbitai resumeto resume the paused reviews. -
@coderabbitai reviewto trigger an incremental review. This is useful when automatic reviews are disabled for the repository. -
@coderabbitai full reviewto do a full review from scratch and review all the files again. -
@coderabbitai summaryto regenerate the summary of the PR. -
@coderabbitai resolveresolve all the CodeRabbit review comments. -
@coderabbitai configurationto show the current CodeRabbit configuration for the repository. -
@coderabbitai helpto get help.
Other keywords and placeholders
- Add
@coderabbitai ignoreanywhere in the PR description to prevent this PR from being reviewed. - Add
@coderabbitai summaryto generate the high-level summary at a specific location in the PR description. - Add
@coderabbitaianywhere in the PR title to generate the title automatically.
CodeRabbit Configuration File (.coderabbit.yaml)
- You can programmatically configure CodeRabbit by adding a
.coderabbit.yamlfile 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.
I noticed that we had again not merged the fix for the export path. I have added the fix again for the examples. I am not sure where it got lost again.
Oh, I think it is still in #214 I will finalize all and merge soon
I will merge this as soon as the checks have run through. We pushed this from one ruff update to the next and had to regularly redo the function variable order change in the examples.