fix(up): handle non-parseable SSH git remote origin gracefully#2741
Merged
Conversation
When the git remote origin uses a non-git@ SSH format (e.g. user@host:owner/repo.git), GitUrl throws Invalid URL which previously crashed the CLI with no useful message. Now: if --url is not provided, a clear error is shown explaining the SSH format limitation and suggesting --url; if a concrete --url is provided, the origin parse error is suppressed and startup continues. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
kptdobe
approved these changes
Jun 11, 2026
Contributor
Author
|
🎉 This PR is included in version 16.20.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
git@SSH URL format (e.g.user@example.ghe.com:ACMEGROUP/racq-eds.git),GitUrlcannot parse it and throwsInvalid URL, which previously crashedaem upwith no useful message--urlis not provided: a clear error now explains the SSH format limitation and suggests using--url--urlis provided: the origin parse error is suppressed and startup continues normally using the provided URLTest plan
shows helpful error when git remote origin uses non-parseable SSH format— verifies the friendly error message and early exitstarts successfully when non-parseable SSH origin is paired with --url— verifies the server starts and_urlis set correctly from the provided--urlnpm testexit 0)🤖 Generated with Claude Code