Right now we have a streamlined workflow where we update contributors in the pyopensci.github.io repo using a cron job that runs
update-contributors
update-reviews
update-review-teams
This allows us to keep all of our current contributor data and review data current on the website.
It would also be useful to be able to run a command that gets all currently open reviews
i have code here that does this BUT because we just updated our API, that code likely needs to be modified.
It could be that the update here is
modify update-reviews to take a input of type single or array that represents labels. then we could do something like
update-reviews -label pyos-accepted to get all reviewers with that label name pyos-accepted
update-reviews -type closed to get all closed reviewers
then we could run an additional step in CI that would get all open reviews, filter out issues that are not reviews
I am not sure what approach here is most efficient but we do need to test open reviews so we know if there are bugs in our API due to how people fill out the issue forms before we accept a package! i am very open to what this workflow looks like.
Right now we have a streamlined workflow where we update contributors in the pyopensci.github.io repo using a cron job that runs
This allows us to keep all of our current contributor data and review data current on the website.
It would also be useful to be able to run a command that gets all currently open reviews i have code here that does this BUT because we just updated our API, that code likely needs to be modified.
It could be that the update here is
modify update-reviews to take a input of type single or array that represents labels. then we could do something like
update-reviews -label pyos-acceptedto get all reviewers with that label name pyos-acceptedupdate-reviews -type closedto get all closed reviewersupdate-reviews -labels array-of-labels-here -type closedthen we could run an additional step in CI that would get all open reviews, filter out issues that are not reviews
I am not sure what approach here is most efficient but we do need to test open reviews so we know if there are bugs in our API due to how people fill out the issue forms before we accept a package! i am very open to what this workflow looks like.