You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 8, 2024. It is now read-only.
As a circle ci user, I would like to able to discover projects in any org via the API. Personally, this is so that I can do extended build statistics in a particular org.
Current workarounds
The current ways to get a list of repositories are very problematic.
The v1 API has an endpoint that lists followed projects https://circleci.com/api/v1/projects. But this lists only my currently followed projects meaning that any program needs maintenance in that its account needs to have all projects followed.
Using the GitHub API to list repositories https://api.github.com/users/cob16/repos and then trying to fetch all of these projects in circle ci. Of course, not all repositories will be set up to use circle ci to this is a very error-prone way to get a list
Suggested new route
The v2 API could have a way to list projects by the organisation
As there is already a GET v2/projects/gh/<org>/<project>route for a single project. An extension to this would be v1/projects/gh/<org> (without the repo name part) that returns a list of projects
The user route could list a user's projects via /v1/user/<org>/projects
As a circle ci user, I would like to able to discover projects in any org via the API. Personally, this is so that I can do extended build statistics in a particular org.
Current workarounds
The current ways to get a list of repositories are very problematic.
The v1 API has an endpoint that lists followed projects
https://circleci.com/api/v1/projects. But this lists only my currently followed projects meaning that any program needs maintenance in that its account needs to have all projects followed.Using the GitHub API to list repositories
https://api.github.com/users/cob16/reposand then trying to fetch all of these projects in circle ci. Of course, not all repositories will be set up to use circle ci to this is a very error-prone way to get a listSuggested new route
The v2 API could have a way to list projects by the organisation
v2/projects/gh/<org>/<project>route for a single project. An extension to this would bev1/projects/gh/<org>(without the repo name part) that returns a list of projects/v1/user/<org>/projects