Skip to content
This repository was archived by the owner on Aug 26, 2026. It is now read-only.
This repository was archived by the owner on Aug 26, 2026. It is now read-only.

Wrong branch name while recreating the quest 03's repo #9

Closed

Description

@MurphyTheMoody

Quest or cheatsheet

Quest 04

Language

English (EN)

Type of improvement

Missing information

Description

Quest 04 Issue:

  • Step 03: If I recreate the quest 03 repo within quest 04 as suggested, the command git push origine main returns error: failed to push some refs to '../archive-centrale.git'. This suggests that git init created a master branch by default, not main.
    Fix:
cd mon-archive
git branch -M main
git push origine main
  • Step 04: the command git clone ./archive-centrale.git ./clone-depuis-bare returns:
Cloning into './clone-depuis-bare'...
done
warning: remote HEAD refers to nonexistent ref, unable to checkout

The bare repo still has its HEAD pointing to master (the git init default), but I pushed main. So it can't find the default branch.
Fix:

git -C ./archive-centrale.git symbolic-ref HEAD refs/heads/main
rm -rf ./clone-depuis-bare
git clone ./archive-centrale.git ./clone-depuis-bare

Step 05 checks returned the following for mon-archive, ma-copie and clone-depuis-bare (respectively):
d2a462c (HEAD -> main, origine/main) Premier parchemin
d2a462c (HEAD -> master, origin/master, origin/HEAD) Premier parchemin
d2a462c (HEAD -> main, origin/main, origin/HEAD) Premier parchemin
verifier.sh still validated the quest, so it's all good in the end ^^

Activity

  1. Dxsk commented on Apr 11, 2026

    @Dxsk
    Owner

    Hey @MurphyTheMoody, thanks a lot for the super detailed report! You nailed a real problem here.

    You actually spotted two things at once:

    1. The quest instructions could be clearer about the git init default branch situation (master vs main) and guide students through the branch rename before pushing.
    2. More importantly, you exposed a rigor gap in verifier.sh itself. The current checks are mostly structural (does the folder exist, is it a git repo, is there a remote) but they never validate the actual names. That is why your setup passed even though you had ma-copie on master, the remote named origine (typo) instead of origin, and a bare repo with a dangling HEAD. The verifier simply was not looking at any of that.

    We just did a full audit of all 20 verifier scripts and quest 04 is one of the worst offenders, along with a few others (09, 12, 17, 19). Thanks to your report, we are going to tighten things up so that students get a clear failure (or at least a loud warning) when their state drifts from what the quest teaches, rather than a silent green check.

    Tracking this as a bug, will update here once the fix lands. Really appreciate you taking the time to write all that up, it made the problem obvious and actionable.

  2. added
    bugSomething isn't working
    on Apr 11, 2026
  3. self-assigned this
    on Apr 11, 2026
  4. Dxsk commented on Apr 16, 2026

    @Dxsk
    Owner

    Hey @MurphyTheMoody, everything you spotted is now fixed on `main` and packaged in the rolling release:

    Sorry for the wait. Rather than shipping a one-line fix for quest 04, I took the time to sweep every quest verifier and every `git init` / remote / branch-name instruction on the critical path, so the same class of bug does not bite the next apprentice somewhere else. That turned into PR #10 with 27 commits across quests 01-20, but the core fixes that unblock your exact scenario are in the Phase A commits.

    Next time you spot a typo or glitch, I will ship the fix much faster. Don't wait on a big sweep - open a fresh issue and it will get its own quick PR. :)

    Thanks again for the detailed repro in the original report, that is exactly what made the full audit possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions