KofTwentyTwo/gclo
2
0 Fork 0
Code Issues 28 Pull Requests 1 Actions Packages Projects Releases 22 Wiki Activity

An empty clone whose first commit has invalid paths can be resolved when the origin's branch has another name #187

New Issue
Open
opened 2026-11-11 05:58:40 +00:00 by james.maes · 0 comments
james.maes commented 2026-11-11 05:58:40 +00:00
Owner
Copy link
Copy source

From the release reviews of 1.1.1 (2026-11-10). Not part of 1.1.1; planned for 1.2.0 unless said otherwise.

What happens

A clone of a repository that was empty, whose HEAD names a branch the origin does not have (the origin's default branch has another name). The origin's first commit has a path Windows cannot create. The pull reports the paths and offers to resolve them; the apply then fails with "This repository has no commits, and neither has its branch on origin".

The pull follows the origin's default branch for such a clone; the path recovery looks only at the branch HEAD names.

Expected

The recovery finds its target the way the pull does.

Reproduced by a reviewer against fixture repositories.

Re-verify against current main before working on it. A fix needs a regression test that fails without it.

From the release reviews of 1.1.1 (2026-11-10). Not part of 1.1.1; planned for 1.2.0 unless said otherwise. ## What happens A clone of a repository that was empty, whose HEAD names a branch the origin does not have (the origin's default branch has another name). The origin's first commit has a path Windows cannot create. The pull reports the paths and offers to resolve them; the apply then fails with "This repository has no commits, and neither has its branch on origin". The pull follows the origin's default branch for such a clone; the path recovery looks only at the branch HEAD names. ## Expected The recovery finds its target the way the pull does. Reproduced by a reviewer against fixture repositories. Re-verify against current `main` before working on it. A fix needs a regression test that fails without it.
james.maes added the bugdeferred labels 2026-11-11 05:58:40 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
.NET
Pull requests that update .NET code
 bug
Something isn't working
 deferred
Agreed follow-up, not scheduled
 dependencies
Pull requests that update a dependency file
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 github_actions
Pull requests that update GitHub Actions code
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 needs-owner
Blocked on an action only the owner can take
 priority
Owner-flagged: work this first
 quality
Standards, simplicity, enforcement
 question
Further information is requested
 refactor
Restructuring without behavior change
 release
Release pipeline / distribution
 wontfix
This will not be worked on
No labels bug deferred
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
forge-recovery (Forge Recovery) james.maes (James Maes)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KofTwentyTwo/gclo#187