A library to easily use git hooks from Dart
To start using Hanzo, add it to your
dev_dependencies and run
To install hooks in your project, run:
$ pub run hanzo install
Now create a matching git hook dart file in
./tool directory (create if needed).
// in ./tool/pre_commit.dart main(List<String> arguments) => print("I'll run before a commit is made!"); // in ./tool/commit_msg.dart main(List<String> arguments) => print("I'll run after commit message is entered!");
|none||If flag is passed it will create a sample pre commit Dart script. Defaults to |
|-k||Creates a bash script for the hook passed, supports passing multiple hooks. Defaults to |
To remove all hooks in your project, run:
$ pub run hanzo remove
Or if you want to remove a specific hook:
$ pub run hanzo remove -k pre-commit -k commit-msg
Git hooks are scripts that run automatically every time a particular event occurs in a Git repository. Hanzo supports all git hooks (https://git-scm.com/docs/githooks)
|Git hook||Dart script name|
Git params will be passed as arguments to the main function of the Dart script.
Please file feature requests and bugs at the issue tracker.
Add this to your package's pubspec.yaml file:
dependencies: hanzo: "^0.1.1"
You can install packages from the command line:
$ pub get
$ flutter packages get
Alternatively, your editor might support
pub get or
Check the docs for your editor to learn more.
Now in your Dart code, you can use:
|0.1.1||Jun 9, 2017|
|0.1.0||Jun 9, 2017|
We analyzed this package on Apr 23, 2018, and provided a score, details, and suggestions below. Analysis was completed with status completed using:
Describes how popular the package is relative to other packages. [more]
Code health derived from static analysis. [more]
Reflects how tidy and up-to-date the package is. [more]
Weighted score of the above. [more]
Detected platforms: Flutter, other
The description is too short.
Add more detail about the package, what it does and what is its target use case. Try to write at least 60 characters.
Package is pre-v1 release.
While there is nothing inherently wrong with versions of
0.*.*, it usually means that the author is still experimenting with the general direction API.
Maintain an example.
Create a short demo in the
example/directory to show how to use this package. Common file name patterns include:
example.dartor you could also use