Question - add a responder similar to what ROS has for approve package

[lwasser]

Hi! ropensci has an approve responder which we could use as well.

Their responder does the following. :

ROpenSci :: Approve
This responder is used to approve a package. It performs a series of tasks:

Adds date-accepted to the body of the issue

Clears reviewers’ current_assignment in AirTable

Creates a new team named like the package-name and invites the creator of the issue to it (owner right needed)

Can reply with a template

Allows labeling

Closes the issue

If the submission-type is stats it checks if stasgrade is present and if so adds the proper label

We'd likely want a subset of this

pyOS Approve

This responder is used to approve a package. It performs a series of tasks:

• Adds date-accepted to the header body of the issue
• Can reply with a template and ingest templated data items into the template such as package-name, reviewer names and author name.
• Allows labeling

How hard would it be to reuse their responder and just remove some of the fancy things such as airtable @xuanxu

[xuanxu]

We can easily have a custom responder for pyOS based on this one.
Actually as we want a lot of commands to interact with a GitHub project board, probably all of the responders we end up using will be custom, based on existing ones but adding or tweaking something.

[lwasser]

thanks @xuanxu i've thought about this more. Now that i see how this works and is setup i'm wondering if we want to stick to the built in responders as much as possible and then add things that i know we'll need (such as the approve responded that ros has - that makes sense). Seeing the challenges that i've already faced in getting the configuration correct 😆 it could make more sense for pyOS to work with mostly things that already exist, customize where it makes most sense (ie approve command and maybe how the issue is setup as we had discussed with the html tags) and then see how that works. i'm leaning that way now.