Revise server side hook configuration to support dynamic hook file extensions.

[jozseffenyes]

Feature Description

In the /modules/git/hook.go file each hook is hardcoded without a file extension, causing inconvenience in deploying any script git hook other than bash on Gitea.

Within modules/git/hook.go, the variable "hookNames" is defined as an array without file extensions:

var hookNames = []string{
    "pre-receive",
    "update",
    "post-receive",
}

Screenshots

No response

[lunny]

How does these hooks with extensions work? https://git-scm.com/docs/githooks

[jozseffenyes]

Hooks with extensions do work on Gitea, but currently, they do not appear on the frontend. It would be helpful to customize each hook's behavior without having to create a wrapper script that calls the script from bash.

For example, if I wanted to create a pre-receive.ps1 script inside the repository on the server, Gitea would not find it since the hook names are hard-coded. Additionally, calling the script from bash with #!/usr/bin/env pwsh without a file extension won't work either, as since PowerShell 7.2 scripts require a .ps1 file extension on windows.

[lunny]

Hooks with extensions do work on Gitea, but currently, they do not appear on the frontend. It would be helpful to customize each hook's behavior without having to create a wrapper script that calls the script from bash.

For example, if I wanted to create a pre-receive.ps1 script inside the repository on the server, Gitea would not find it since the hook names are hard-coded. Additionally, calling the script from bash with #!/usr/bin/env pwsh without a file extension won't work either, as since PowerShell 7.2 scripts require a .ps1 file extension on windows.

I don't think so. Gitea will create update.d, proc-receive.d, post-receive.d and pre-receive.d. You can put your scripts under these folders.