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

Pipelines in 'Create Project' page are confusing

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
30/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
领域
design, frontend

调研方向

从 Create Project 页面开始,检查列出的四个内置流水线是如何呈现和选择的。定义更简单的分组或命名方式,以及 UI 应用于自动选择的输入;完成的标准是,新手无需依赖重叠的术语即可区分适用的流水线。

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

描述

enhancement web-ui

Several of the ScanCode.io v35.3.0 built-in pipelines are confusing - to me and others they look to be doing roughly the same thing.

Talking about pipelines in below table - for a user new to ScanCode.io the words "analyze", "inspect", "resolve" and "scan" all basically mean the same. The static and dynamic resolving of dependencies seems "bolted on" to me.

Believe we should simplify the current built-in pipelines for a better user experience so the user is more likely to instantly pick the pipeline that's applicable to their use case. Ideally the UI would be 'smart' - meaning based on given inputs try to automatically select the pipeline that is most relevant

Pipeline Description
inspect_packages Inspect a codebase for packages and pre-resolved dependencies.
resolve_dependencies Resolve dependencies from package manifests and lockfiles.
scan_codebase Scan a codebase for application packages, licenses, and copyrights.
scan_single_package Scan a single package archive (or package manifest file).
主要语言
Python
星标
223
派生
214
平均合并
2 天 3 小时
30 天内合并 PR
13

环境准备

从这里开始

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

aboutcode-org/scancode.io 的其他 Issue

查看 aboutcode-org/scancode.io 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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