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

kci command line tool rework

未关闭
  • 哪里不对？
#2,125 1 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@JenySadadia 已经在做这个了。

开始于 2024年2月16日。

评估

这个 Issue 还没有评估数据。

描述

roadmap

The kci command is to the new API & Pipeline what the kci_* tools were for the legacy system. It needs to be clearly designed to ease adoption by the community as a tool for KernelCI core developers but also any member of the kernel ecosystem: kernel developers, test system developers etc. I should help with prototyping features by hand before automating them with services running event loops and also work hand-in-hand with the new web dashboard.

Several aspects need to be considered, in particular: feature set, ease of implementation and maintenance of the code, direct user experience, documentation, accessibility.

Here are some of the topics as part of the preparation work:

Based on the outcome of these, here's the list of tasks to complete:

  • Legacy code moved to kernelci.legacy
  • New kci entry point command implemented using chosen framework
    • #2133
  • TOML settings features integrated with arguments parsing and secrets
    • #2129
  • Common options and CLI framework
    • #2178
    • #2195
    • #2230
    • #2233
  • Required set of sub-commands implemented
    • kci user
      • #2141
      • #2183
      • #2084
      • #2205
      • #2239
      • #2236
    • kci config
      • #2138
      • #2226
    • kci job
      • #2220
      • #2227
    • kci node
      • #2204
      • #2231
    • kci event
      • #2203
    • kci storage
      • #2161
    • #2134
  • Documentation updated accordingly
    • HTML / Markdown for online pages
    • man pages and offline help

Some follow-up GitHub issues will be created for additional commands such as kci view, kci bisect, kci email etc.

主要语言
Python
星标
120
派生
110
平均合并
8 小时 1 分钟
30 天内合并 PR
13

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

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

kernelci/kernelci-core 的其他 Issue

查看 kernelci/kernelci-core 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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