GITHUB API v4 - 按问题数量排序存储库
GITHUB API v4 - Order repositories by number of issues
如何根据打开的问题数量从查询中排序存储库?
https://developer.github.com/v4/input_object/repositoryorder/
最好使用 GitHub GraphQL V4
GitHub chose GraphQL for our API v4 because it offers significantly more flexibility for our integrators.
The ability to define precisely the data you want—and only the data you want—is a powerful advantage over the REST API v3 endpoints.
GraphQL lets you replace multiple REST requests with a single call to fetch the data you specify.
例如,您可以 get the total number of issues 在一个 repo 上使用:
{
repository(owner: "facebook", name:"react") {
issues {
totalCount
}
}
}
returns:
{
"data": {
"repository": {
"issues": {
"totalCount": 5308
}
}
}
}
查看来自 Fábio Molinar 的文章“Using Github’s GraphQL to retrieve a list of repositories, their commits and some other stuff — part 2”,列出存储库并应用该过滤器。
.
如何根据打开的问题数量从查询中排序存储库?
https://developer.github.com/v4/input_object/repositoryorder/
最好使用 GitHub GraphQL V4
GitHub chose GraphQL for our API v4 because it offers significantly more flexibility for our integrators.
The ability to define precisely the data you want—and only the data you want—is a powerful advantage over the REST API v3 endpoints.
GraphQL lets you replace multiple REST requests with a single call to fetch the data you specify.
例如,您可以 get the total number of issues 在一个 repo 上使用:
{
repository(owner: "facebook", name:"react") {
issues {
totalCount
}
}
}
returns:
{ "data": { "repository": { "issues": { "totalCount": 5308 } } } }
查看来自 Fábio Molinar 的文章“Using Github’s GraphQL to retrieve a list of repositories, their commits and some other stuff — part 2”,列出存储库并应用该过滤器。 .