Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[Suggestion] Repos endpoint improvement

未关闭
#2,208 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
28/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
github, openapi
领域
api

调研方向

首先查看 /users/user/repos 端点的 OpenAPI 描述,并将其与 issue 中提到的 languages_url 端点进行比较。确定附加语言数据预期的结构和命名方式。当提案形成一致同意的 API 契约并完成相应的描述更新后,工作即告完成。

由索引模型根据 Issue 内容生成。

描述

feature fundamentals-and-support P4 shield waiting for review

Hello, I was not sure where to write this issue, so I decided to dump my thought here and hope that somebody would pass it on to the right people. (sorry about that)

I noticed that the /users/user/repos endpoint returns a language property, but I'd like to see another key implemented such as languages or language_details that contains data from the languages_url endpoint. This would be cool to see as currently if a dev wishes to get all the languages of their repos, they would quickly exceed their API rate limit quote (50 public repos, let's say, all of which's languages you want to fetch).

Thanks for reading and I hope that somebody kind enough passes this on to a Github dev/engineer and I would like to hear feedback on my suggestion.

主要语言
没有语言数据
星标
1.6k
派生
342
平均合并
2 小时 23 分钟
30 天内合并 PR
57

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

github/rest-api-description 的其他 Issue

查看 github/rest-api-description 的全部 Issue

相似的 Issue

更多 Backend & API Design Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。