prepare-commit-msg | Automatically prefix commit messages | Version Control System library

The best way to handle this is indeed to use the prepare-commit-msg hook. When you create one, you should take note of the arguments passed to it, and, unless you want to make your life needlessly difficult, avoid modifying it when you're using git commit --amend (such as when the second argument is commit).

Note that the hook needs to modify the file that's the first argument in place, which is different from what many people expect. As such, you will often want to use something like the -i argument to Perl, Ruby, or sed, or a scriptable line editor like ed -s or ex -s with the w command.

If you're trying to add a trailer, then git interpret-trailers may be helpful to add the entry you desire based on the config, and you can customize it to not add an entry if one is already present. It can't use user.team, but it can use other configuration options to set the trailer.

An example where you're trying to simply replace a %(team) token from the template with the value of user.team looks like this:

Because of the way the initial commit message is produced, it seems there's no easy way to leverage directly that code (see my edit).

A manual rewrite is needed, but as it turned out, it's not that difficult to achieve. This is a prepare-commit-msg hook that does what I wanted:

From the looks of it, you have several hooks installed.

The one that triggers on git push is pre-push.

If you don't remember/don't know how it was installed and what it does, you can inspect its content by opening .git/hooks/pre-push in an editor.

From the looks of it : it tries at least to run the typescript compiler on your project.

The initial message you mention is just a warning message, and shouldn't be the cause of your failed job. You should inspect the errors mentioned after that to have a pointer to what is actually refused by the compiler.

As said in the comments by @AlexeyLarionov : you should see the same errors from your ide, or by invoking tsc from the command line on your project.

Figured it out - it was simple. I needed to add the following to husky:

As I found out, the solution was to Upgrade from WSL1 to WSL2, there mounting works correctly. I'm able to git-add or git-clone without permission errors now.

Open a PowerShell to see your current version:

Write you script like that with the sh shebang and check it with https://www.shellcheck.net/

If everything is ok with the sh shebang, it means the script will work ok with any version of bash, zsh, or whatever POSIX shell interpreter. MacOS's BSD type environment may have tools with different syntax or at least lacking the GNU CoreUtils specific features, so be cautious not to use these specific options when running commands.