Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate chatops-style PR management #2776

Open
matthewturk opened this issue Jul 23, 2020 · 5 comments
Open

Investigate chatops-style PR management #2776

matthewturk opened this issue Jul 23, 2020 · 5 comments
Labels
code style Related to linting tools infrastructure Related to CI, versioning, websites, organizational issues, etc proposal Proposals for enhancements, changes, etc

Comments

@matthewturk
Copy link
Member

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

@matthewturk matthewturk added proposal Proposals for enhancements, changes, etc infrastructure Related to CI, versioning, websites, organizational issues, etc code style Related to linting tools labels Jul 23, 2020
@munkm
Copy link
Member

munkm commented Jul 23, 2020

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

@matthewturk
Copy link
Member Author

matthewturk commented Jul 23, 2020 via email

@munkm
Copy link
Member

munkm commented Jul 23, 2020

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

@matthewturk
Copy link
Member Author

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
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code style Related to linting tools infrastructure Related to CI, versioning, websites, organizational issues, etc proposal Proposals for enhancements, changes, etc
Projects
None yet
Development

No branches or pull requests

3 participants