github - Do "chunked" pushes to remote Git repo? -


We want to push 20.00+ local GIT repositories for the blame but it has come to know that transfer is not a problem GitHub actually does not process more than 1000 drawbacks in one time ("Process" which means they will add links to issues).

Therefore, to be able to correctly transfer this protected and it has been processed correctly, we should move at once to the "block" of more than 1000 in one. But how?

We tried to walk back in history in some way, moving forward in the block and moving forward every time, but we should use the wrong "order" because it is the result of many problems.

provided that you can run the following script:

  #! BIN / BASH GIT Push Original Master ~ $ i: Master GIT Push Original Owner: Master  

This will be repeated from 20000 to 0 / $ I ($ 20000-900) And the reader commits with the remote branch master .

Master ~ n is Git syntax and n \ first committed master .


Comments