We just tested this branch in our environment. It does not 100% fulfill our needs, as we need the script being executed additionally and not as alternative. (We want to install npm modules) Therefore we removed the "exit 0". Maybe this is something which could be considered in this PR, otherwise we will create another PR for this use case.
Furthermore it is not clear to us what the expected behaviour should be in case the script is not found or returns with an error. We observed that the deploy.sh.tmpl loops when the custom script exits with non-zero value.
We just tested this branch in our environment. It does not 100% fulfill our needs, as we need the script being executed additionally and not as alternative. (We want to install npm modules) Therefore we removed the "exit 0". Maybe this is something which could be considered in this PR, otherwise we will create another PR for this use case.
Furthermore it is not clear to us what the expected behaviour should be in case the script is not found or returns with an error. We observed that the deploy.sh.tmpl loops when the custom script exits with non-zero value.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
See #6
highly appreciated if this would be merged. :)
We just tested this branch in our environment. It does not 100% fulfill our needs, as we need the script being executed additionally and not as alternative. (We want to install npm modules) Therefore we removed the "exit 0". Maybe this is something which could be considered in this PR, otherwise we will create another PR for this use case.
Furthermore it is not clear to us what the expected behaviour should be in case the script is not found or returns with an error. We observed that the deploy.sh.tmpl loops when the custom script exits with non-zero value.