Fuzzy schedule scattering fails to parse GHE SSH remote URLs

[anthonymastreanvae]

Summary

gh aw compile emits the warning:

⚠ Fuzzy schedule scattering without repository context. Workflows with the same name in different repositories may collide. Ensure you are in a git repository with a configured remote.

…even when inside a valid git repository with a single origin remote configured.

Environment

• gh aw (latest as of 2026-05-08)
• Git remote: example@example.ghe.com:example-org/example-repo.git (SSH, GHE)
• Single remote named origin
• Inside git work tree (confirmed via git rev-parse --is-inside-work-tree)

Steps to Reproduce

1. Clone a repository from a GitHub Enterprise instance using SSH (user@host:owner/repo.git format)
2. Add a workflow with a fuzzy schedule (e.g., schedule: daily around 10am on weekdays)
3. Run gh aw compile

Expected Behavior

The compiler extracts example-org/example-repo from the origin remote URL and uses it as the schedule scattering seed — no warning emitted.

Actual Behavior

The compiler fails to parse the SSH remote URL and falls back to warning about missing repository context.

Workaround

Pass --schedule-seed explicitly:

gh aw compile --schedule-seed "example-org/example-repo"

Analysis

The remote URL format example@example.ghe.com:example-org/example-repo.git is a valid SCP-style SSH URL. The parser likely only handles:

• git@github.com:owner/repo.git
• https://github.com/owner/repo.git

…and doesn't account for GHE instances with custom usernames or hostnames in SCP-style URLs. The general pattern <user>@<host>:<owner>/<repo>.git should be supported.

---

Issue drafted with GitHub Copilot ✨