Git clone particular version of remote repository

Question

I cloned a remote git repository about a month ago  The remote repository has undergone many changes and has now become unstable  Now I need another copy of the repository  version identical to the one I cloned a month ago   How do I do this

User · Answer

Probably git reset solves your problem   git reset --hard - commit hash-

User · Answer

Use git log to find the revision you want to rollback to  and take note of the commit hash  After that  you have 2 options    If you plan to commit anything after that revision  I recommend you to checkout to a new branch  git checkout -b  lt new branch name gt   lt hash gt  If you don t plan to commit anything after that revision  you can simply checkout without a branch  git checkout  lt hash gt  - NOTE  This will put your repository in a  detached HEAD  state  which means its currently not attached to any branch - then you ll have some extra work to merge new commits to an actual branch    Example     git log commit 89915b4cc0810a9c9e67b3706a2850c58120cf75 Author  Jardel Weyrich  lt suppressed gt  Date    Wed Aug 18 20 15 01 2010 -0300      Added a custom extension   commit 4553c1466c437bdd0b4e7bb35ed238cb5b39d7e7 Author  Jardel Weyrich  lt suppressed gt  Date    Wed Aug 18 20 13 48 2010 -0300      Missing constness     git checkout 4553c1466c437bdd0b4e7bb35ed238cb5b39d7e7 Note  moving to  4553c1466c437bdd0b4e7bb35ed238cb5b39d7e7  which isn t a local branch If you want to create a new branch from this checkout  you may do so  now or later  by using -b with the checkout command again  Example    git checkout -b  lt new branch name gt  HEAD is now at 4553c14    Missing constness    That way you don t lose any informations  thus you can move to a newer revision when it becomes stable

User · Answer

You could  reset  your repository to  any commit you want  e g  1 month ago     Use git-reset for that   git clone  remote address here  my repo cd my repo git reset --hard  ENTER HERE THE COMMIT HASH YOU WANT

User · Answer

You Can use simply   git checkout  commithash   in this sequence  git clone  URLTORepository  cd  into your cloned folder  git checkout commithash   commit hash looks like this  45ef55ac20ce2389c9180658fdba35f4a663d204

User · Answer

If that version you need to obtain is either a branch or a tag then   git clone -b branch or tag name repo address or path

User · Answer

Unlike centralized version control systems  Git clones the entire repository  so you don t only get the current remote files  but the whole history  You local repository will include all this   There might have been tags to mark a particular version at the time  If not  you can create them yourself locally  A good way to do this is to use git log or perhaps more visually with tools like gitk  perhaps gitk --all to see all the branches and tags   If you can spot the commits hashes that were used at the time  you can tag them using git tag  lt hash gt  and then check those out in new working copies  for example git checkout -b new branch name tag name or directly with the hash instead of the tag name

User · Answer

The source tree you are requiring is still available within the git repository  however  you will need the SHA1 of the commit that you are interested in  I would assume that you can get the SHA1 from the current clone you have   If you can get that SHA1  the you can create a branch   reset there to have the identical repository   Commands as per Rui s answer

User · Answer

uploadpack allowReachableSHA1InWant  Since Git 2 5 0 this configuration variable can be enabled on the server  here the GitHub feature request and the GitHub commit enabling this feature   Bitbucket Server enabled it since version 5 5    Usage     Make remote with 4 commits  and local with just one  mkdir server cd server git init touch 1 git add 1 git commit -m 1 git clone       local for i in  2  4   do     touch   i      git add   i      git commit -m   i  done    Before last commit  SHA3    git log --format   H  --skip 1 -n1     Last commit  SHA4    git log --format   H  -n1      Failing control without feature  cd    local   Does not give an error  but does not fetch either  git fetch origin   SHA3    Error  git checkout   SHA3     Enable the feature  cd    server git config uploadpack allowReachableSHA1InWant true    Now it works  cd    local git fetch origin   SHA3  git checkout   SHA3    Error  git checkout   SHA4

User · Answer

You can solve it like this   git reset --hard sha   where sha e g   85a108ec5d8443626c690a84bc7901195d19c446  You can get the desired sha with the command    git log

[git] Git clone particular version of remote repository

Examples related to git

Examples related to git-clone