Investigate chatops-style PR management

[matthewturk]

Especially now with black and isort and other linting that gets run, we may want to explore having chatops-style PR management to make things easier for contributors.

Specifically, something like:

https://github.com/peter-evans/slash-command-dispatch

and

peter-evans/slash-command-dispatch#11

[munkm]

This seems like a nice tool. do you know how the history works with these?

[matthewturk]

So I think that it looks just like regular commits! https://github.com/peter-evans/slash-command-dispatch/pull/11/commits

…

On Thu, Jul 23, 2020 at 10:36 AM Madicken Munk ***@***.***> wrote: This seems like a nice tool. do you know how the history works with these? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2776 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAVXO63AEBJJLLVXOFIHUTR5BKH7ANCNFSM4PFZB6PA> .

[munkm]

Ah, I meant authorship (sorry for being ambiguous), but it looks like your link answered that question too!

[matthewturk]

I've experimented with this here:

matthewturk#4

and this is the slash command dispatch repo I set up:

https://github.com/matthewturk/slash-command-processor

I'm going to be issuing a PR shortly that adds slash commands, but before it will work, we need to have that repository transferred here. I'm nervous about just transferring it -- anybody listening think it's a bad idea?

[brittonsmith]

I think this is ok to do (transferring the repo).