You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 5, 2018. It is now read-only.
In classes that use the fork strategy, teachers may leave students' pull requests open for review, so that they can submit updates, etc. This may leave them with a bunch of open pull requests across one or more repositories, so it would be helpful to have a command that takes care of them in bulk.
My thinking is to expand merge_pull_requests:
$ teachers_pet help pull_requests
Usage:
teachers_pet pull_requests --repository=OWNER/REPO
Options:
--repository=OWNER/REPO
--merge # Merges pull requests. Cannot be used in combination with --close.
--close # Closes pull requests. Cannot be used in combination with --merge.
...
Perform an action on all open pull requests in a particular repository
On the fence about whether it should be an even more generic issues command, though that may be confusing since most people probably think about them (and treat them) as separate things.
The text was updated successfully, but these errors were encountered:
In classes that use the fork strategy, teachers may leave students' pull requests open for review, so that they can submit updates, etc. This may leave them with a bunch of open pull requests across one or more repositories, so it would be helpful to have a command that takes care of them in bulk.
My thinking is to expand
merge_pull_requests
:On the fence about whether it should be an even more generic
issues
command, though that may be confusing since most people probably think about them (and treat them) as separate things.The text was updated successfully, but these errors were encountered: