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

Canned responses to automate common replies #331

Open
tiran opened this issue Apr 18, 2021 · 3 comments
Open

Canned responses to automate common replies #331

tiran opened this issue Apr 18, 2021 · 3 comments

Comments

@tiran
Copy link
Member

tiran commented Apr 18, 2021

Would it be possible to extend Bedevere's vocabulary and teach him canned responses? This would reduce the burden on code reviewers and give users better and more consistent answers. There are issues that pop up in regular intervals, e.g. missing CLA, rebase required, broken tests, missing blurb. In other cases users have ignored Bedevere's instructions and have used GH's review request feature instead of Bedevere command I have made the requested changes; please review again. It would be helpful to re-trigger Bedevere's response, too.

Example

Command: /bedevere blurb

Bederve replies: A Python core developer has requested a news entry. <instruction how to add a blurb>.

@Mariatta
Copy link
Member

It's possible. We need to implement and also document all the commands somewhere.

To avoid spam, perhaps the commands should be restricted to: Python core devs, Python triage, and the OP.

@Mariatta
Copy link
Member

Also do we want this all part of bedevere codebase, as a new GitHub Action within the CPython repo? What are your recommendations @brettcannon ?

@brettcannon
Copy link
Member

I personally would rather either pick apart Bedevere to become a bunch of individual GitHub Actions for easier maintenance, or move Bedevere over wholesale as a GitHub Action.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants