-
Notifications
You must be signed in to change notification settings - Fork 263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using pre-commit #1347
Comments
👋 Hello @lnxpy, thanks for your interest in EVA DB 🙏 Please visit our 🔮 Tutorials to get started, where you can find quickstart guides for simple tasks like Image Classification all the way to more interesting tasks like Emotion Analysis. If this is a 🐞 Bug Report, please provide a minimum reproducible example to help us debug it. If this is a ❓ Question, please provide as much information as possible, including dataset examples and query results. |
Could you add more details on how you plan to use pre commit to improve the experience? Thanks! |
Hi @xzdandy. Sure. The only checkpoint that you have in your docs is checking the formatting of changes via Black. We can automate that process and ensure that the devs do format their changes before making any PR. |
Yes. Sounds good to me! |
Search before asking
Description
Use pre-commit for a better Development Experience and more stable contributions.
Use case
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: