search for: natfriedman

Displaying 5 results from an estimated 5 matches for "natfriedman".

2019 Mar 20
2
[cfe-dev] [lldb-dev] [GitHub] RFC: Enforcing no merge commit policy
...nterprise Server' >> plan, which is for self-hosted github instances. >> > > AIUI, the GitHub team is perfectly willing to help out the LLVM project in > whatever way LLVM needs, including but not limited to turning on > server-side hooks for us. > https://twitter.com/natfriedman/status/1086470665832607746 > > Server-side hooks are *the *answer to this problem. There is no problem. > You just use a server-side hook. > > (Whether or not to use GitHub PRs is an orthogonal question. You can use > hooks with PRs, or hooks without PRs; PRs with hooks, or PRs wi...
2019 Mar 20
3
[lldb-dev] [GitHub] RFC: Enforcing no merge commit policy
On 03/20/2019 10:41 AM, Zachary Turner wrote: > > > On Tue, Mar 19, 2019 at 12:00 PM Tom Stellard via lldb-dev <lldb-dev at lists.llvm.org <mailto:lldb-dev at lists.llvm.org>> wrote: > > Hi, > > I would like to follow up on the previous thread[1], where there was a consensus > to disallow merge commits in the llvm github repository, and start a
2019 Mar 20
5
[cfe-dev] [lldb-dev] [GitHub] RFC: Enforcing no merge commit policy
...39; >> plan, which is for self-hosted github instances. >> >> >> AIUI, the GitHub team is perfectly willing to help out the LLVM project in whatever way LLVM needs, including but not limited to turning on server-side hooks for us. >> https://twitter.com/natfriedman/status/1086470665832607746 >> >> Server-side hooks are *the *answer to this problem. There is no problem. You just use a server-side hook. >> >> (Whether or not to use GitHub PRs is an orthogonal question. You can use hooks with PRs, or hooks without PRs; PRs with ho...
2019 Mar 19
8
[GitHub] RFC: Enforcing no merge commit policy
Hi, I would like to follow up on the previous thread[1], where there was a consensus to disallow merge commits in the llvm github repository, and start a discussion about how we should enforce this policy. Unfortunately, GitHub does not provide a convenient way to fully enforce this policy. We can enforce it for pull requests, but not for direct pushes to the master branch, so we will have to
2020 Jan 23
4
[cfe-dev] Phabricator -> GitHub PRs?
On Wed, Jan 22, 2020 at 5:19 PM David Greene <greened at obbligato.org> wrote: > Hubert Tong <hubert.reinterpretcast at gmail.com> writes: > > > It was already mentioned earlier in the thread that: > > - The individual commits cannot be approved in the sense of approving a > PR. > > Later conversation makes me wonder how often that really happens though.