configuring pre-commit
See original GitHub issue🚀 Feature
Setting up pre-commit for DeepChem developers.
Motivation
New DeepChem devs often run into formatting issues (mypy, yapf, flake8, etc.). pre-commit
(or something else like it) allows a one-time configuration of pre-commit hooks that devs can use to automatically make sure their code complies with DeepChem’s formatting standards.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
pre-commit
The pre-commit config file describes what repositories and hooks are installed. ... The hook mapping configures which hook from the repository is used...
Read more >pre-commit-config.yaml - GitHub
A framework for managing and maintaining multi-language pre-commit hooks. - pre-commit/.pre-commit-config.yaml at main · pre-commit/pre-commit.
Read more >Getting Started with Python Pre-commit Hooks
Pre-commit hooks are a subset of Git hooks. ... All we need to do is create and format a .pre-commit-config.yaml file within our...
Read more >PreCommit Hooks! - Medium
To set up our Pre-commit hook we would be using Husky which describes itself as — 'Git hooks made easy'. Let's get started...
Read more >How to use git pre-commit hooks, the hard way and the easy ...
pre-commit -config.yaml file is ready, run pre-commit install to install/set up the hooks specified in your configuration file. At this point, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Absolutely, a contribution here would be very helpful! Feel free to tag me on a Work-in-Progress PR as you get started.
@ncfrey Sorry for the late response (got caught up in NeurIPS 😅). I’ve added references to why certain choices for pytest and specific releases were made in the PR. LMK how it looks.