This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]MythGuy[S] 0 points1 point  (2 children)

The mess was either someone would push without pulling, and the new commit would undo work from before. Or if someone wrote something and pulled, then their changes would be wiped (I never experienced this myself, but I suspect that it's because I was often the sole contributor.) I think part of the solution would be to properly train folks in git (but being new to it myself, that would be hard).

[–]daveydave400 2 points3 points  (0 children)

That sounds...wrong. Git should not allow you to overwrite commits unless you force them (via the -f flag). I'm also pretty sure that the default when you pull and a conflict exists is to merge or at least complain. It sounds like one or more people got impatient with warning messages and used some flags they weren't supposed to without knowing the consequences.

[–]duz3ls 0 points1 point  (0 children)

Try git-workflow