Allow project / GitHub repo addition to recognize bare clones
- 主要语言
- 没有语言数据
- 星标
- 2.1k
- 派生
- 153
- PR 合并指标
- 30 天内没有已合并 PR
描述
### Feature summary
_No response_
### What problem are you trying to solve?
When adding a project or GitHub repository, the current flow does not recognize repositories that are bare clones. This makes the repo appear unsupported or unavailable even though it is a valid repository state.
### Proposed solution
Update the repository/project addition flow to detect bare clone repositories and treat them as valid inputs for addition. If there are any limitations, surface a clear message explaining the constraint instead of failing silently or rejecting the repo outright.
### Workflow impact
This would remove a setup blocker for users working with bare clones and make repository onboarding more reliable, especially in environments where repositories are mirrored or managed in bare form.
### Installation context
GitHub App repository addition flow
### Additional context
If relevant, the repository may be managed as a bare clone rather than a working tree checkout.
贡献指南
调研方向
从 GitHub App 仓库添加流程开始,追踪它如何验证没有 working tree 的仓库。先检查 bare clone 的情况,然后定义支持的行为和清晰的限制说明;当 bare clone 可以被添加,或被拒绝并给出明确解释时,即表示完成。
由索引模型根据 Issue 内容生成。
评估
- 领域
- developer-experience
- Issue 类型
- 功能
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 冷清
- 描述清晰度
- 基本清楚
- 新手友好度
- 45/100