[Toybox] GitHub Apps - Repo Lockdown · GitHub

[enh]

On Sun, Aug 16, 2020 at 8:14 PM Rob Landley <rob at landley.net> wrote:
>
> On 8/16/20 2:31 PM, enh via Toybox wrote:
> > https://github.com/apps/repo-lockdown
> >
> > Turns out there is a way to automate telling folks with pull requests to try the
> > mailing list instead. See link.
> >
> > (This came up on the tzdata mailing list. I have no personal experience.)
>
> Eh, its not a huge deal. The list is my personal preference, but wget pull
> request plus ".patch" on the end feeds straight into "git am".

yeah, i've certainly seen you apply patches sent as pull requests. i
think the bigger problem is that checking pull requests isn't part of
your workflow in the same way that checking the list is. i'd almost
responded on https://github.com/landley/toybox/pull/234 that the
submitter should try sending their patch to the mailing list instead,
for example.

> There's a generational divide between old people who grew up on mailing lists
> and younguns who grew up on web forums. People young enough that "here's a list
> of 37 websites that went away, you can't archive this and will lose your
> history" gets responded to with "I was 4 when that happened, who cares what
> happens in 10 years that's forever, we'll burn that bridge when we come to it,
> and just because it's happened like clockwork for decades doesn't mean it'll
> happen AGAIN"...
>
> As I said, "wide net". The real history is the git commit log I suppose...

i think the question is which is a worse experience for those younger
than we mailing list types --- having a pull request automatically
closed with a "try the mailing list instead" or having a pull request
accidentally missed because the person who needs to see it mainly
concentrates on the mailing list?

i'm happy to be the manual nag bot though. for example:
https://github.com/landley/toybox/pull/234 :-)

> Thanks for the pointer though.
>
> Rob