mookme icon indicating copy to clipboard operation
mookme copied to clipboard

A pre-commit tool designed for monorepos.

Results 27 mookme issues
Sort by recently updated
recently updated
newest added

Hi, and thanks for developing this great tool! **Unexpected behavior:** When applying the hooks with Mookme, the hooks are run with the working tree as-is, as far as I understand....

bug
enhancement
help wanted

Fixes #92 by offering a `maxDepth` parameter in the `.mookme.json` file. Also updated the docs

Hi, My project folders in the monorepo sometimes are under 4 levels of directories, and because of that Mookme doesn't find them. Would it be possible to make maxDepth parameter...

enhancement
ready

I was wondering why you decided to name the Mookme hooks directory '.hooks' instead of '.mookme'. Naming directories after the project seems to be a convention used by a lot...

enhancement
v3

When using the argument `{matchedFiles}` for instance in a hook, it will list changed file of the package as expected, but it will also list deleted files, leading to errors...

bug

https://github.com/axtgr/wildcard-match is used for matching the `onlyOn` attribute. Unfortunately `wildcard-match` does not support features like brace expansion (e.g. `**/*.{js,ts}` to match `.js` and `.ts` files). Maybe it would be an...

enhancement
ready

`mookme init` writes the actual git hook scripts into `.git/hooks`. Since 2.9, git itself supports changing the path in which git looks up the hooks scripts to some place in...

enhancement
good first issue
ready

Works fine on macOS when using Git CLI, but fails on Windows when using GitHub Desktop.

The path to the file names are enclosed in quotes so that it can add files with symbols and spaces. resolves #121