Incorrect implementation for git fetch/pull with colon ":" affecting remoteAdvance6 about learngitbranching HOT 4 CLOSED

Good catch! Do you think just switching to commit hashes instead would solve the inconsistency but still provide a valuable lesson?

from learngitbranching.

Definitely that could be a workaround until it’s fixed on the simulator, although I think the most common way of using the colon fetch is with a branch name origin (updating o/branch)

from learngitbranching.

Alright @juanmv94 just updated the level -- let me know what you think:
https://learngitbranching.js.org/?NODEMO&command=level%20remoteAdvanced6

from learngitbranching.

More issues discovered affecting fetch and pull commands:
I'm making a pull request fixing all these issues including the previous ones

git fetch origin foo:bar (with HEAD on o/foo up to date, bar branch still doesn't exists) --> Already up to date!

Examples:

git clone
git fetch origin main:foo

git fetch origin foo:bar (with current HEAD not part of history of foo) --> Your origin branch is out of sync with the remote branch and fetch cannot be performed

Examples:

git checkout -b foo c0
git commit
git clone
git fetch origin main:bar

git clone
git fetch origin c0:foo

from learngitbranching.