18 releases (7 stable)
|1.4.0||May 22, 2019|
|1.3.0||Jan 24, 2019|
|1.2.1||Dec 13, 2018|
|1.2.0||Oct 15, 2018|
|0.0.6||Oct 2, 2018|
#33 in Development tools
1,536 downloads per month
Used in 19 crates
cargo-husky is a development tool to set Git hooks automatically on
cargo test. By hooking
cargo test automatically, it prevents broken codes from being pushed to a remote
cargo-husky crate to
[dev-dependencies] section of your project's
[dev-dependencies] cargo-husky = "1"
Then run tests in your project directory.
$ cargo test
Check Git hook was generated at
cargo-husky generates a hook script which runs
cargo test by default.
#!/bin/sh # # This hook was set by cargo-husky v1.0.0: https://github.com/rhysd/cargo-husky#readme # Generated by script /path/to/cargo-husky/build.rs # Output at /path/to/target/debug/build/cargo-husky-xxxxxx/out # set -e echo '+cargo test' cargo test
Note: cargo-husky does nothing on
cargo test when
- hook script was already generated by the same version of cargo-husky
- another hook script put by someone else is already there
To uninstall cargo-husky, please remove
cargo-husky from your
[dev-dependencies] and remove
hook scripts from
Behavior of cargo-husky can be customized by feature flags of
You can specify them in
[dev-dependencies.cargo-husky] section of
Cargo.toml instead of adding
[dev-dependencies.cargo-husky] version = "1" default-features = false # Disable features which are enabled by default features = ["precommit-hook", "run-cargo-test", "run-cargo-clippy"]
This configuration generates
.git/hooks/pre-commit script which runs
cargo test and
All features are follows:
||See below section||Disabled|
If generated hooks by
run-cargo-clippy features are not sufficient for you,
you can create your own hook scripts and tell cargo-husky to put them into
.cargo-husky/hooksdirectory at the same directory where
.gitdirectory is put.
- Create hook files such as
pre-commit, ... as you like.
- Give an executable permission to the files (on *nix OS).
features = ["user-hooks"]to
[dev-dependencies.cargo-husky]section of your
- Check whether it works by removing an existing
targetdirectory and run
your-repository/ ├── .git └── .cargo-husky └── hooks ├── post-merge └── pre-commit
[dev-dependencies.cargo-husky] version = "1" default-features = false features = ["user-hooks"]
cargo-husky inserts an information header to copied hook files in
.git/hooks/ in order to detect
self version update.
Note that, when
user-hooks feature is enabled, other all features are disabled. You need to prepare
all hooks in
Build scripts are intended to be used for building third-party non-Rust code such as C libraries. They are automatically run on compiling crates.
cargo-husky crate is added to
dev-dependencies section, it is compiled at running tests.
At the timing, build script is run and sets Git hook automatically.
The build script find the
.git directory to put hooks based on
$OUT_DIR environment variable
which is automatically set by
cargo-husky puts Git hook file only once for the same version. When it is updated to a new version, it overwrites the existing hook by detecting itself was updated.
cargo-husky is developed on macOS and tested on Linux/macOS/Windows with 'stable' channel Rust toolchain.