ngraham: This is fantastic! It would be even better if you could feed it a group to subscribe to everything in that whole group, rather than having to give it individual repos.
Hmm, I won't use /groups/frameworks/projects as it is paginated by 20 projects (the next url is in the HTTP header). It looks like a simple list is in /groups/frameworks which I can use to build the issues url.
~~So it would make 165 requests just for frameworks. I'll have to look into if there's a rate limit for
the public API. I may need to add the ability to add a user generated API token.~~
Hmmm.
Hmm, I won't use /groups/frameworks/projects as it is paginated by 20 projects (the next url is in the HTTP header). It looks like a simple list is in /groups/frameworks which I can use to build the issues url.
~~So it would make 165 requests just for frameworks. I'll have to look into if there's a rate limit for the public API. I may need to add the ability to add a user generated API token.~~
Nevermind, it's way easier than that as there is:
As for parsing groups in the config? I guess we can assume
/frameworksis a group? Though that might get confused if I add support for/user.We could force the user to use one of these urls as they start with
/groups/