fix(git): prevent fatal error for missing 'origin' remote - #871
Merged
Conversation
BYK
approved these changes
Aug 10, 2026
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
1 participant
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.
The
getDefaultBranchfunction insrc/utils/git.tspreviously relied ongit remote set-head <remoteName> --autoto determine the default branch. If the specified remote (e.g., 'origin') did not exist in the repository, this command would fail with a generic git error: "fatal: 'origin' does not appear to be a git repository" (exit code 128).This fix introduces an explicit check within
getDefaultBranchto verify the existence of theremoteNameusinggit.getRemotes(). If the remote is not found, aConfigurationErroris now thrown with a clear, actionable message, guiding the user or test environment to correctly configure the remote. This prevents the propagation of an opaque git error and provides a better debugging experience, especially in isolated test setups like thecraft-verify-bun-lockscenario.Fixes CRAFT-2P
Comment
@sentry <feedback>on this PR to have Autofix iterate on the changes.