Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: "<org>/*" for the repo name #51

Open
sminnee opened this issue Jan 15, 2019 · 5 comments
Open

Suggestion: "<org>/*" for the repo name #51

sminnee opened this issue Jan 15, 2019 · 5 comments
Labels
enhancement help wanted Anyone is free to try and tackle this issue

Comments

@sminnee
Copy link
Contributor

sminnee commented Jan 15, 2019

Sometimes it will be helpful to pull in all repositories of a github organisation.

For this purposes it would be good to support "/*" as a repo name. You would want to be able to combine it with other repos so that for example you could configure the repo list as: silverstripe/* symbiote/silverstripe-advancedworkflow

I would imagine that this could be implemented as a preprocessor that expanded such entries on the repo list before commencing. At the same time as implementing this, a de-duplication filter might also be of use.

@luandy64
Copy link
Contributor

Would having a stream that hits this endpoint be the same as what you are describing?

@sminnee
Copy link
Contributor Author

sminnee commented Jan 30, 2019

Sort of. We need to hit that endpoint, and then use the results to adjust the value of repos before this for loop:

https://github.com/singer-io/tap-github/blob/master/tap_github.py#L481

Simply adding that endpoint as a stream wouldn't get the issues, pull requests, commits, etc, for each of those repositories.

@luandy64 luandy64 removed the question label Feb 4, 2019
@louisguitton
Copy link

that would be awesome 👏

@osterman
Copy link

Hello from Cloud Posse! We are large open source maintainers. We have over 300 projects on GitHub (all actively maintained) that we manage and would like to do a better job handling the metrics. This tap is almost perfect as-is, but we cannot easily manage this config with so many repos, so a wildcard would be desired.

@luandy64 luandy64 added enhancement help wanted Anyone is free to try and tackle this issue labels May 29, 2019
@tinydylan
Copy link

My suggestion in #74 is basically a duplicate of this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement help wanted Anyone is free to try and tackle this issue
Projects
None yet
Development

No branches or pull requests

5 participants