ehmatthes/gh-profiler

What's faster: gh, or an API call?

开放

#53 创建于 2026年5月16日

 (6 条评论) (0 个反应) (0 位负责人)Python (12 个派生)github user discovery
good first issuehelp wanted

仓库指标

星标
 (122 个星标)
PR 合并指标
 (平均合并 13天 19小时) (30 天内合并 3 个 PR)

描述

When examining a user's profile and recent activity, we're only looking at public information. I started this using gh because it makes it easy to make api calls. But it has the drawback of requiring that people have the gh CLI tool installed. I believe the one thing we're getting from gh that might be hard to replicate as well with a public API call is the correct remote to look at, when processing PR and issue numbers. It's still worth considering http API calls, because then only some actions would depend on having gh installed.

Some starting questions and tasks:

  • Consider a current call that's made: gh api users/ehmatthes --jq '{login, name, created_at, company, blog, location, email, bio}'
    • What's the equivalent public API call over http?
    • Is there any meaningfully different response time between the two calls?
    • Are there any gh calls in the project that can't be replaced with a public API call?

贡献者指南