Git Basics: Unrelated histories pitfall about curriculum HOT 2 CLOSED

Thanks for opening the issue!

I'd like to add that once this happens, it is easily solved by git pull --allow-unrelated-histories. But anybody new to git will not know that and I don't think it's a given that they will find somebody on the Discord that knows about it either. This can be a big source of frustration for new learners.

It's probably not possible to avoid it completely, since it already only happens if the student does not follow instructions 100%. But I think the priority goal should be to reduce the likelihood of it happening early on.

from curriculum.

Thanks for submitting this! I agree that this is something we've seen a lot.

I would be on board with a note or rewording of what we currently have in the recipes project to be more assertive that people should more than likely go back and look at the instructions on setting a repo up again.

I think I would be against us even mentioning git pull --allow-unrelated-histories though. I don't think we should be enabling people to essentially disable some of the safety features built into git.

from curriculum.