fix(deps): setup clones master, the branch these repos actually have - #99
Merged
srpatcha merged 2 commits intoSep 1, 2026
Merged
Conversation
`ebuild setup` clones eos and eBoot at the branch named in DEFAULT_CONFIG.
Both entries named "main". Neither repository has a main -- both default
to master -- so the clone failed for every new developer, before any
build could run:
$ git ls-remote --heads .../eos.git main # no output
efirmware, in the same mapping, already names master; only the two that
matter for a first `setup` were wrong.
tests/unit/test_sources_are_importable.py asserts each configured branch
exists upstream and has been failing on this, which the suite could not
report while collection was broken.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
18 tasks
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.
ebuild setup— the first command a new developer runs — clones eos and eBoot at the branch named inDEFAULT_CONFIG. Both entries namemain. Neither repository has amain:So
setupfails for every new developer, before any build can run.efirmware, in the same mapping, already namesmaster— only the two that matter for a firstsetupwere wrong.tests/unit/test_sources_are_importable.py::test_default_repo_branch_exists_upstreamasserts each configured branch exists upstream and has been failing on exactly this, which the suite could not report while collection was broken (#97).🤖 Generated with Claude Code