-
Notifications
You must be signed in to change notification settings - Fork 216
Display pull request mergeable status on "gh pr" list #305
Comments
👍 |
Nice idea @mdelapenya! The good news is that a https://developer.github.com/v3/pulls/#mergability The bad news is that it's only available when you fetch each PR separately and not when you list all of them like we do nowadays. |
And how about adding a command to the gh pr, like:
which retrieves one pull request at a time, displaying its comments, mergeable status, or/and whatever a reviewer will need before starting the review? That will follow the API for one single pull |
Nice idea. I've made some modifications and it already works, but it's not ready for release yet. @mdelapenya, can you take a look at https://developer.github.com/v3/pulls/#get-a-single-pull-request and please tell me what else you'd find it useful for the --info command to give? Should it show always everything or the --details flag should add something more? Best regards, |
Let's start with the mergeable status and the comments on the pull. I guess we can improve later Thanks @henvic!! |
Any update on this? :) |
@mdelapenya I am planning to do this on the weekend. |
@mdelapenya can you please try the new --info command? I have not added comments just yet, but will pretty soon. For now --list isn't showing if the pull request is mergeable because it would make --list painfully slow. If GitHub starts to provide this info on their public API I will update. Is that ok? I have contacted GitHub to ask them if there's any chance they'd add this on the list API method. |
|
Hi Henrique, thanks for the follow-up of this ticket! I understand the problem, so for me, current --info command could be enough
Maybe we could follow a color code for mergeable status, just the same in the real UI. What do you think? |
Sometimes reviewers don't even visit github to see their pending pull requests list, because it's easier executing:
I'd like to see the mergeable status of the pull request, so that reviewer can see if the pull is good to merge or not.
The text was updated successfully, but these errors were encountered: