On 03/21/2019 10:32 AM, Pavel Labath via llvm-dev wrote: > On 21/03/2019 13:12, David Chisnall via lldb-dev wrote: >> On 20 Mar 2019, at 18:23, Arthur O'Dwyer via cfe-dev >> <cfe-...@lists.llvm.org> wrote: >>> >>> Server-side hooks are the answer to this problem. There is no problem. You >>> just use a server-side hook. >> >> It is quite unlikely that GitHub will allow LLVM (or any other project) to >> run arbitrary post-receive hooks. > > What about a single, simple, specific post-receive hook that has been vetted > by the github team, and that cannot by changed from the LLVM side without > going through their customer support team (and additional vetting)?
GitHub already has something like this, called branch protections[1]. There just isn't a 'no merge commit' protection, but this is something I'm going to request. -Tom [1] https://help.github.com/en/articles/configuring-protected-branches > _______________________________________________ > LLVM Developers mailing list > llvm-...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev _______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
