Remapping hostname prevents using `gh stack submit`

Open

#337 opened on Jul 28, 2026 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 55/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Quiet
Tech stack: go
Domain: cli

Research direction

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.

Written by the indexing model from the issue text.

Description

bug topic: cli - submit

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

Dominant language: Go
Stars: 1.5k
Forks: 73
Avg merge: 1d 8h
Merged PRs (30d): 7

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

Textual definition update: Update description of GO:0141014 please Open

textual definition

Difficulty 1/5 Under an hour Newbie friendliness 90/100

geneontology/go-ontology#32653 · Opened Sep 23, 2026
harbor-db: missing STOPSIGNAL turns every container stop into an unclean shutdown Open

Difficulty 1/5 Under an hour Newbie friendliness 75/100

goharbor/harbor#23989 · Opened Sep 23, 2026
Use Prometheus-compatible _total suffix for counter metrics Open

needs design

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

canonical/pebble#1098 · Opened Sep 23, 2026
scripts/acceptance.sh times out: acceptance package needs longer than go test's 10m default Open

Priority/High ready-for-agent Severity/Major Type/Bug

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

wso2/wso2-cli#235 · Opened Sep 23, 2026
Sort the dokku_domains set and clear plan mutations Open

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

dokku/docket#556 · Opened Sep 23, 2026

More Go issues