In Git, does origin track local commits before pushing? -


itemprop = "text">

Long story short, a co-worker's computer crashed and lost its work with its last push. As a last resort, I thought that before they were originally transferred from the original to the local, before it was ascertained to what extent the origin was revealed. If the original is working at some temporary place, does it anyway come back to the code?

In GIT, the remote only "tracks" through a different repository through two * mechanisms: fetch , in which they explicitly request references, and push , in which reference is provided to them from any other repository

If the entire local drive has become corrupted, and now you can save most of the .git directory in the repository, then you are sadly limited to the drive recovery Methods - GIT can not help you beyond this: Sorry ((

If you have a repository and it's just in a bad condition, then the git reflog command can help you , Or if you offer more specificity then you can do something Deep spellanking of the object database.

* There are definitely other mechanisms to do this, but they use these things and their equivalent flourish under the hood.

Comments

Popular posts from this blog

Python SQLAlchemy:AttributeError: Neither 'Column' object nor 'Comparator' object has an attribute 'schema' -

java - How not to audit a join table and related entities using Hibernate Envers? -

mongodb - CakePHP paginator ignoring order, but only for certain values -