Hi Ben,

I know other large multi-repository projects have opted to have an empty "issues-only" repository to tackle this.

You can aggregate reasonably easily as-is, though. Some examples:

open CCPPETMR issues: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3ACCPPETMR
open CCPPETMR PRs: https://github.com/issues?q=is%3Aopen+is%3Apr+user%3ACCPPETMR
open CCPPETMR anything: https://github.com/issues?q=is%3Aopen+user%3ACCPPETMR

all CCPPETMR anything: https://github.com/issues?q=user%3ACCPPETMR

Regards,

Casper

On 21 July 2017 at 12:49, Thomas, Ben <[log in to unmask]> wrote:

Hi Casper,

The topic of GitHub issues came up during the t-con this morning and Kris asked that I send you a message. Currently, CCPPETMR GitHub issues/milestones are spread across 3 repositories. Do you know if it is feasible to aggregate the issues somehow, rather than having to visit each independently? And if so, how?

Kind regards,

Ben