Scenario 1: fail to push because the tip of the current branch is behind
The situation is exactly the scenario 2 in the last blog, but, with the need changed, I made a wrong decision, I reverted to a prior commitment, and proceeded with my job on that version, then when I tried to push the new commitments to the server, I got error:
The only one solution I figured out is to create a new branch from the commitment that I went back to, and the following commitments will go along the new branch, so create a branch:
So the branches now look like:
1938
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
