Skip to content

Add pre-commit framework config.#3

Open
ellieayla wants to merge 1 commit intoSiteRelEnby:mainfrom
ellieayla:pre-commit-framework-support
Open

Add pre-commit framework config.#3
ellieayla wants to merge 1 commit intoSiteRelEnby:mainfrom
ellieayla:pre-commit-framework-support

Conversation

@ellieayla
Copy link
Copy Markdown
Contributor

When multiple tools want to use the same .git/hooks/pre-commit script, need a framework to config and run them.

https://pre-commit.com/ is the current standard. Add .pre-commit-hooks.yaml.

When multiple tools want to use the same .git/hooks/pre-commit script, need a framework to config and run them.
@SiteRelEnby
Copy link
Copy Markdown
Owner

SiteRelEnby commented Apr 11, 2026

looks like language: unsupported_script means pre-commit won't install leash itself, so it already needs to be installed through the repo directions including making sure it's in $PATH, should add that to the readme. Otherwise someone might add the yaml config and wonder why they get leash: command not found.

Also, current release is v0.1.2, not 3. Otherwise, looks good.

@ellieayla
Copy link
Copy Markdown
Contributor Author

ellieayla commented Apr 11, 2026

language: unsupported_script means pre-commit won't "install" leash, it'll just clone the repo and execute leash directly from within, without being on the PATH. Did you pre-commit try-repo ../local/path/to/repo/of/git-leash/? Did it not do that?

(And I stuffed a hypothetical future version v0.1.3 in there because pre-commit shallow-clones the cited repo at the cited tag when trying to find .pre-commit-hooks.yaml - it definitely won't find the file at v0.1.2!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants