On 12/5/2018 4:53 PM, Rene Rivera via Boost wrote:
> On Wed, Dec 5, 2018 at 3:50 PM Edward Diener via Boost <
> [hidden email]> wrote:
>> On 12/4/2018 10:34 AM, Rene Rivera via Boost wrote:
>>> GitHub doesn't allow those server side hooks.
>> Are you saying that we have no access to the .git or .git/hooks
>> subdirectory of a Github hosted repository ?
> GitHub doesn't allow running scripts on their servers.
Ok. Then the best alternative is to write a client-side commit hook.
Am 05.12.18 um 23:43 schrieb Gavin Lambert via Boost:
>> GitHub doesn't allow running scripts on their servers.
> You can write a webhook to run a script on a different server. But at
> best this could yell at someone after the fact; it can't prevent
> accepting a push (although it can mark a pull request as invalid --
> that's how the CI hooks in).
Simply do it in CI. All Boost builds are run (at least) on travis,
right? So all you need is a simple shell script (or a one-liner in
.travis.yml) that finds executable files with a forbidden suffix and
returns a message and error status code when found. This will block all
PRs and also flag commits pushed directly.
Client-side hooks are worthless for that as you can't force everyone to