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

`--version` argument in `kup install` doesn't disambiguate between paths and branch names

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

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
python
领域
cli

调研方向

Start at the kup install argument parsing and version-resolution flow, then trace how --version values are classified as branch names or local paths. Reproduce the collision described with a matching branch and directory, and define completion as a warning plus an explicit way for users to choose the intended interpretation.

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

描述

When a user runs kup install ... --version ..., the --version argument can be either a branch name or a path. If there is both a branch and a local directory with the same name, kup interprets it as a path by default. This might lead to a user accidentally installing the wrong version without realizing.

For example, say that a user is in their local clone of the kontrol repo, and runs kup install kontrol --version feature, with the intention of installing the current version of the feature branch from the external repo. However, they forgot that they had a feature directory inside their local kontrol clone where they checked out feature (for example, with git worktree add feature) and made local changes that they didn't push to the external repo. kup install kontrol --version feature will actually interpret feature as the path to the local feature directory, rather than the name of the external feature branch. As a result, the version that is installed will be different than the one the user expects without them realizing.

Ideally, I think that if the --version argument can be interpreted both ways, it might be a good idea to warn the user and provide a way to allow them to disambiguate between the two, so that this mistake can be avoided.

主要语言
Python
星标
10
派生
2
PR 合并指标
30 天内没有已合并 PR

环境准备

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

从这里开始

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

runtimeverification/kup 的其他 Issue

查看 runtimeverification/kup 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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