Indeed. Much of the time the job of teasing out the requirements is half the job. That's my argument for companies to use "domain" programmers: they have the unarticulated requirements inside them, and their process of development teases those requirements out, no meetings required.

>I wrote a program of a few lines that does the job, using vfp as the scripting language. It's easy once you know what the requirements are. Like everything in life, no?
>
>
>
>>Hi Alex,
>>
>>Have you look at PowerShell? https://git-scm.com/book/en/v2/Git-in-Other-Environments-Git-in-Powershell
>>
>>Hank
>>
>>>Hi,
>>>
>>>I need to create some scripts to run in git hooks. In https://www.atlassian.com/git/tutorials/git-hooks there is the following information:
>>>
>>>

Scripting Languages
>>>
>>>The built-in scripts are mostly shell and PERL scripts, but you can use any scripting language you like as long as it can be run as an executable. The shebang line (#!/bin/sh) in each script defines how your file should be interpreted. So, to use a different language, all you have to do is change it to the path of your interpreter.

>>>
>>>Can someone explain how to use that method to tell git to use a windows friendly scripting language?
>>>
>>>TIA,
>>>
>>>Alex