This repository was archived by the owner on Sep 10, 2026. It is now read-only.
Repository navigation
Stop claiming a cloned repository scaffolds - #44
Merged
Merged
Conversation
The changeset said an empty destination covers "cloning a repository with no first commit". It does not: a clone leaves `.git`, which is refused like any other entry. That text becomes the published 0.9.0 changelog, so it would have promised `git clone && create-eigen-game` works. The `destinationProblem` comment repeated the same claim, and now says why the case is not supported rather than implying it is — publishing into a clone means parking `.git`, renaming staging over the top and putting it back, with a failure in the middle able to orphan a remote. Release PR #42 has not consumed the changeset yet, so this still lands in the same release. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Correction to #43, which is merged but not released — Release PR #42 still has the changeset, so this lands in the same 0.9.0.
The changeset was wrong, and it is the published changelog. It said the empty-destination allowance covers "cloning a repository with no first commit". A clone leaves
.git, whichdestinationProblemrefuses like any other entry — verified:So the note as written promised
git clone && create-eigen-gameworks, when it does not.The
destinationProblemdoc comment carried the same claim and now states why the case is unsupported instead of implying it is: publishing into a clone means parking.git, renaming staging over the top and putting it back, with a failure in the middle able to orphan a remote — a lot of care for a flow whose alternative is scaffolding beside it and moving the result in.No behaviour change. Text only.
🤖 Generated with Claude Code