anttiah

I was so upset about this change that I forgot to add repro steps. Sorry for that. I have now added the missing details to the original message.

> Why cannot you add .ps1 extension? As stated in the description, it's required by Git: https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks > To enable a hook script, put a file in the hooks subdirectory...

> That's weird at least on Linux it works for me This issue originated from https://github.com/PowerShell/PowerShell/pull/15859 which was for Windows only.

> I wonder on Windows if it might work to allow for `pwsh -file foo`, but instead of straight execution, we save it to a temporary .ps1 and then execute...

Windows has many file types that can be, from the user's point-of-view, executed without extension. For example, `.exe`, `.bat`, `.cmd` and, as far as I know, every other file type...

> Why don't Git like file extensions? In Unix-like systems the piece of information that tells the operating system that file is executable is an attribute of the underlying file...

> That doesn't really help explain why the hook can't just have the `.ps1` extension. It should still work through the shebang as all that has now changed is that...

List of supported hooks is indeed hard-coded. It's defined here: https://git-scm.com/docs/githooks. Abstracting the steps in the work flow from the actual file names would definitely make things easier on the...

Those kind of shims might work in limited set of cases where input is not needed, but some of the hooks get their input from `stdin` and are expected to...

Same issue here. I'm stuck with the branch specified in the project from which my inventory is sourced. I've tried all kinds of workarounds, like daisy-chaining two job templates in...