GHPullRequest for more than one Repo

[namanbada0606]

Describe the bug
Firstly wanted to say BIG THANK YOU for this great library, it's really my team a big way.

Context:
Class GHPullRequest currently handles for one repo to pull PR, how do I leverage the same for more than one repo? Is this a currently limited to ONE ?

To Reproduce
Steps to reproduce the behavior:

clone https://github.com/sebkur/github-cli

./gradlew clean create

./scripts/hubcli list-pull-requests

Expected behavior
We should require more than one repo

Desktop (please complete the following information):

• OS: MAC
• Browser CHROME
• Version 73

[bitwiseman]

@namanbada0606
Glad you are enjoying it.

This library generally has attempted to match the GitHub REST API behavior with some improvements to make things all little smoother where possible.

Each Pull Request is part of as single repository. I'm unclear about what the behavior it is you'd like to see. What would you like to be able to do after ./scripts/hubcli list-pull-requests above? Could you describe the steps you'd like to perform in a little more detail (not in terms of the build process for an different project?

Thanks!

[namanbada0606]

Thank you @bitwiseman for your comments, Here is what i'm using currently

./scripts/hubcli list-pull-requests myOrg/myRepo

Its basically runs -

java ListPullRequests myOrg/myRepo

This is returning PRs mapped to myRepo while i wish to do this for more repo's under same "myOrg"

For instance:
./scripts/hubcli list-pull-requests myOrg/myRepo1, myOrg/myRepo2, myOrg/myRepo3

So that under one Org with diff reports i can produce a single report

Thanks

[bitwiseman]

@namanbada0606 This sounds like an issue to be fixed in the https://github.com/sebkur/github-cli project. Or as a new layer of this project (it is outside the scope of the current " match the GitHub REST API behavior" philosophy). Or it could be done using GitHub v4 GraphQL API, but that is also outside the current scope.

[namanbada0606]

Ah! It's ideal to support at this library level instead of the app

[bitwiseman]

@namanbada0606
Perhaps. As I said, I'd be open to someone starting a new layer/package in this project that provides more high-level behavior. Now that we have a test framework that makes it feasible. Do you have time to take that on?

[namanbada0606]

Sure, No worries.