It appears to me that what is described as "Developing hooks interactively" is very limited in its usage, but I'm probably just misunderstanding how to do it. While I can point to a Git repository on my file system, I still need to commit in that repository, and push to the remote, since pre-commit autoupdate or similar commands try to git clone and git reset X --hard where X is a SHA or a branch name or something like that. It would be more useful to point to a file location, and make ongoing changes there, test the changes iteratively, then commit these changes. It is also unclear what the meaning of sha: ... is in this configuration. There may not really be a problem here, except that I don't understand things 😉
It appears to me that what is described as "Developing hooks interactively" is very limited in its usage, but I'm probably just misunderstanding how to do it. While I can point to a Git repository on my file system, I still need to commit in that repository, and push to the remote, since
pre-commit autoupdateor similar commands try togit cloneandgit reset X --hardwhereXis a SHA or a branch name or something like that. It would be more useful to point to a file location, and make ongoing changes there, test the changes iteratively, then commit these changes. It is also unclear what the meaning ofsha: ...is in this configuration. There may not really be a problem here, except that I don't understand things 😉