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

Automate skill label generation

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

还没有人认领这个 Issue。

  • #121 来自 @Cronus1007 —— 已关闭,未合并

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
python
领域
tooling

调研方向

首先,将当前的 skills.json 与每个仓库的 cc-metadata.yml 中的技术条目进行比较。确定该功能应该替换 skills.json、扩展元数据,还是将两者结合起来,然后定义技术数据如何转化为同步的技能标签。当维护者不再需要手动维护这些标签的最新状态时,即视为完成。

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

描述

🌟 goal: addition 💬 talk: discussion 💻 aspect: code 🤖 aspect: dx 🟩 priority: low 🧹 status: ticket work required

Problem

Skill labels need to be manually set up in skills.json. This

  • increases manual work on the part of repo maintainers to ensure that the skills listed in a different repo (this one) are up to date
  • causes redundancy of information that is already present in cc-metadata.yml under the technologies key in each repo

Description

The technologies key could be expanded to a more verbose structure to describe languages, libraries and frameworks and then used to eliminate the need for skills.json entirely. This presents benefits such as

  • richer information about the technological make-up of our projects
  • automated sync of labels with technologies

Alternatives

The improvements to .cc-metadata.yml can be a good-to-have part of the feature if there isn't a consensus to proceed with that. But the automation of skill labels is still beneficial. Also it does not have to be binary, a combination of .cc-metadata.yml and skills.json would also be a fine solution.

Implementation

  • I would be interested in implementing this feature.
主要语言
Python
星标
20
派生
19
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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