Remapping hostname prevents using `gh stack submit`
- 主要语言
- Go
- 星标
- 1.5k
- 派生
- 70
- 平均合并
- 1 天 8 小时
- 30 天内合并 PR
- 7
描述
I use a synthetic hostname mapping in `~/.gitconfig` (1) in conjunction with my `.ssh/config` (2) to select the SSH host key and user identity. In this case, the synthetic hostname is `fastalyze.github.com`. When I run `gh stack submit` this happens:
```
gh stack submit
Checking stack state...
✗ failed to create GitHub client: determining repository: unable to determine current repository, none of the git remotes configured for this repository point to a known GitHub host
```
I suspect there is a check for stacked PR support based on the hostname, and it's not recognizing `fastalyze.github.com`.
(1) `~/.gitconfig` stanza:
```
[url "git@fastalyze.github.com:fastalyze/"]
insteadOf = git@github.com:fastalyze/
[url "git@fastalyze.github.com:fastalyze/"]
insteadOf = https://github.com/fastalyze/
```
(2) `.ssh/config` stanza:
```
host fastalyze.github.com
Hostname github.com
User "jeff-younker"
IdentityFile ~/.ssh/id_fastalyze
IdentityAgent none
```
贡献指南
调研方向
Start at the `gh stack submit` entry point and reproduce the repository-detection failure using the supplied `.gitconfig` and `.ssh/config` mappings. Trace how the remapped hostname is checked against known GitHub hosts; done when `gh stack submit` recognizes this configuration and proceeds without breaking normal GitHub remote detection.
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- go
- 领域
- cli
- Issue 类型
- 缺陷
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 活跃度
- 冷清
- 描述清晰度
- 基本清楚
- 新手友好度
- 55/100