You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
parseGitHubRemote / parseAzureDevOpsRemote fail on repo names containing dots #1077
squad watch fails with Could not detect platform: Could not parse GitHub remote URL: <url> when the origin remote points to a repo whose name contains a . character (e.g. https://github.com/myorg/my.repo.name.git).
For https://github.com/myorg/JADE.xlighthousepipelines.git:
owner captures myorg
repo group can only match up to (but not including) the first ., so it tries JADE
the optional (?:\.git)?$ then needs to match .xlighthousepipelines.git$ — it doesn't
[^/.] can't consume the . to extend, so the entire match fails and parseGitHubRemote returns null
The error then bubbles up from createPlatformAdapter in packages/squad-sdk/src/platform/index.ts and becomes the Could not detect platform: ... fatal in packages/squad-cli/src/cli/commands/watch/index.ts.
GitHub allows . in repo names (other than the leading-dot / . / .. special cases), so this is a legitimate parsing miss rather than user error.
Same bug in Azure DevOps parser
parseAzureDevOpsRemote has the same ([^/.]+?) repo capture in all three of its regexes (dev.azure.com HTTPS, ssh.dev.azure.com SSH, legacy *.visualstudio.com), so any ADO repo with a dot in its name will also fail to parse.
Proposed fix
Change the repo capture group from [^/.]+? to [^/]+? in all four regexes. The trailing (?:\.git)?$ plus the non-greedy quantifier still strip a trailing .git correctly while preserving dots inside the repo name.
Activity
vejadu commentedon May 4, 2026
Fix proposed in #1078.
fix(platform): allow dots in repo names when parsing remote URLs
fix: 5 bug fixes — dotted repos, icon spacing, board owner, charter, …