After a few reverts, and the re-base turtoise git began to behave strangely. There is a remote main branch, when I create my checkout -b on its basis, then an incorrect branch is created. Inaccurate in the fact that right after creation, push (to the main branch) is not empty. It contains the same left commit. The only way out is to create a branch remotely in github or demolap .
Closed due to the fact that the essence of the question is incomprehensible by the participants aleksandr barakin , Streletz , D-side , Nick Volynkin ♦ 8 Jun '16 at 0:57 .
Try to write more detailed questions. To get an answer, explain what exactly you see the problem, how to reproduce it, what you want to get as a result, etc. Give an example that clearly demonstrates the problem. If the question can be reformulated according to the rules set out in the certificate , edit it .
- First idea: a local branch is created based on a remote tracking branch, which does not correspond to the remote branch, because there was some kind of rollback on the remote. You can check this pool pull. - Nick Volynkin ♦
- And what happens if you create a branch from the console? - Nick Volynkin ♦
- made a pool, everything is normal. After pushing a clean branch, I tried to compare it and the trunk. Here's what appeared: you need to get a valid comparison. - voipp
- hmm The message is as if one of the proposed objects is invalid, it is not. - Nick Volynkin ♦
- and the repository is closed? Is it possible to look at it somehow? By the way, it can earn if you re-clone. I have not met with this, but it feels as if reefs are confused in the remote tracking branch somewhere. Also - for compare, can you use the used command? - Nick Volynkin ♦
|