Investigate the built-in git from the TwinCAT XAE shell and figure out how to configure it to run the pre-commit hooks properly
I started investigating this a little bit using the TwinCAT installed on the programming node. In the TwinCAT docs, the interface appears to have more configuration options than mine does in Tools > Options > Source Control, where I only have the option of changing my source control plug-in. I assume this means that the git plugin doesn't have any configuration options.
I peeked at the pre-commit hook script generated on Windows and the shebang looks like:
#!/usr/bin/env python.exe
I'm not sure if this leads to any clues, or if modifying this default script will be the path forward.
As an aside, there will need to be extra effort to get this working at all on the programming node due to the airgap
Investigate the built-in git from the TwinCAT XAE shell and figure out how to configure it to run the
pre-commithooks properlyI started investigating this a little bit using the TwinCAT installed on the programming node. In the TwinCAT docs, the interface appears to have more configuration options than mine does in Tools > Options > Source Control, where I only have the option of changing my source control plug-in. I assume this means that the git plugin doesn't have any configuration options.
I peeked at the pre-commit hook script generated on Windows and the shebang looks like:
#!/usr/bin/env python.exeI'm not sure if this leads to any clues, or if modifying this default script will be the path forward.As an aside, there will need to be extra effort to get this working at all on the programming node due to the airgap