25 releases

0.11.2 Jun 23, 2020
0.10.3 Feb 25, 2020
0.10.1 Oct 14, 2019
0.9.1 Jul 21, 2019
0.1.2 Dec 27, 2018

#52 in Development tools

Download history 5841/week @ 2023-08-06 6652/week @ 2023-08-13 5526/week @ 2023-08-20 5919/week @ 2023-08-27 6003/week @ 2023-09-03 7661/week @ 2023-09-10 6831/week @ 2023-09-17 6329/week @ 2023-09-24 6607/week @ 2023-10-01 6124/week @ 2023-10-08 6125/week @ 2023-10-15 6345/week @ 2023-10-22 5142/week @ 2023-10-29 5498/week @ 2023-11-05 6689/week @ 2023-11-12 4773/week @ 2023-11-19

22,495 downloads per month
Used in 83 crates

MIT license

1.5K SLoC


Git hook utility for Rust codebases that lets you run any script for any git hook.

Functional, but still in Beta!

Version Badge Downloads Badge License Badge

Linux CI Badge Mac CI Badge Windows CI Badge
Test Results Badge Coverage Badge

Quick Start

Pre-requisites: Make sure you have Rust installed and that Cargo's bin directory is on your PATH. https://www.rust-lang.org/tools/install

  1. Add rusty-hook as a dev dependency in your Cargo.toml file
  2. Run cargo test (to build your dev dependencies, including rusty-hook)
  3. Update the generated .rusty-hook.toml file with the commands you want to run
  4. Run git commit (or equivalent to trigger your git hook)!
    • You may also want to have your hook script fail (for example add a failing test if your commit hook is cargo test) to see the hooks be enforced.
    • note the very first (and only) time you do this will take an extra ~30 seconds or so to finalize the setup


Just add rusty-hook as a dev dependency in your Cargo.toml file:

rusty-hook = "^0.11.2"


When you add rusty-hook as a dev-dependency in your project, it will automatically configure the git hooks once it is built (for example the first time you run cargo test).

This will ensure that all of the client side git hooks are setup and available, and it will create a rusty-hook configuration file if one does not already exist.

The git hook script will ensure that the rusty-hook cli is available, so the very first time a git hook is triggered on your machine you will see a message indicating that the rusty-hook setup is being finalized which may take ~30 seconds or so:

Finalizing rusty-hook configuration...
This may take a few seconds...

(Optional) Install

You can also install the rusty-hook cli with cargo:

cargo install rusty-hook

You can optionally manually initialize any git directory by running the init command in any git directory to set it up:

rusty-hook init


You define your desired git hook configuration in the rusty-hook configuration file (a TOML file named .rusty-hook.toml or rusty-hook.toml).

Here's an example rusty-hook configuration that leverages multiple git hooks, including the pre-commit and the pre-push hooks:

pre-commit = "cargo test"
pre-push = "cargo fmt -- --check"
post-commit = "echo yay"

verbose = true


Under the [hooks] table, you can add an entry for any and every git hook you want to run by adding a key using the name of the git hook, and then specify the command/script you want to run for that hook. Whenever that git hook is triggered, rusty-hook will run your specified command!


Under the [logging] table, you can control whether to log the output of running your specified hook commands. By default rusty-hook will log the results of your hook script, but you can disable this behavior by setting the verbose key to false:

verbose = false


There's a few other git hook utilities available on crates.io, but none of them quite suited our needs so we made rusty-hook!


All contributions are welcome and appreciated! Check out our Contributing Guidelines for more information about opening issues, developing, and more.

Removing rusty-hook

We'll be sad to see you go, but here's what to do if you'd like to remove rusty-hook from your project.

  1. Remove the rusty-hook dev dependency from the Cargo.toml file in your project.
  2. Remove the .rusty-hook.toml configuration file from your project.
  3. Remove the git hook scripts that were placed in the git hooks directory in your local project workspace (this is typically in the .git/hooks/ directory). Note that if you were using rusty-hook version 0.9.1 or newer and you skip this step, then the git hooks will still be invoked as part of your git workflow and you will see the following warning message on git commit:
rusty-hook git hooks are configured, but no config file was found
In order to use rusty-hook, your project must have a config file
See https://github.com/swellaby/rusty-hook#configure for more information about configuring rusty-hook

If you were trying to remove rusty-hook, then you should also delete the git hook files to remove this warning
See https://github.com/swellaby/rusty-hook#removing-rusty-hook for more information about removing rusty-hook from your project

Please also consider opening an issue to report any bugs/problems you experienced, missing features, etc. so that we can work on improving rusty-hook!


~36K SLoC