Download older version of github file

Connect and share knowledge within a single location that is structured and easy to search. I have a version of a. I have the sha1 hash value for the commit that has the version of that file that I want. I do not want to replace the current version of the file. Rather, I want to just get a separate copy of it that reflects its state at the older version. The file I am interested in originally existed in the top-level directory of the repository. I am currently in a sub-directory of the repository trying to run this command so as to get the older version of file.

You can use git cat-file to dump the contents of the file to the standard output and redirect that into your desired destination:. Also, that may not work in older versions of git, in which case you'd need to explicitly supply the full path to the file relative to the repository's root. I think that the best solution is to overwrite temporally your file.

In your top-level of your repository:. In contrast to checking out a file, show does not intrinsically change your workspace, you can do anything you like with the output. Credit to this answer , and of course see full details in the manual. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Note: If you're still displaying the GitHub bootcamp section, it'll show up underneath it.

When creating a repository you have a few things to decide including it's name and whether it'll be publicly accessible or not. Choosing a name should be pretty simple because you likely already have a name for your project. If you're just following along for learning purposes, use 'Hello-World. Because spaces and special characters will cause problems.

Keep it simple and easy to type in the command line. If you want to include a more complex name, you can add it to the optional description field beneath the name field. If you're creating an open-source project, you want a public repository. If you want to code by yourself or share only with specific people, a private repository will do. Make the choice that works best for you and your project.

When you're all done, you can click the 'Create repository' button but you might want to do one other thing first: check the 'Initialize this repository with a README' checkbox. Ideally that file would contain a little information about your project, but you might not want to deal with that right now. For the purposes of this tutorial, we're going to leave the box unchecked because, in the next section, we're going to create a README file from scratch to practice committing sending it to GitHub.

When you send files to GitHub, you commit them. Before you start, you need to know where your local code repository is on your computer and how to access it via the command line. In this tutorial, we're going to assume there's a directory called 'Hello-World' in your computer's home folder.

Now that your repository is ready, type this:. If you already had a repository ready to go, you'd just need to cd to that directory and then run the git init command in there instead. Either way, your local repository is ready to go and you can start committing code. But wait, you don't have anything to commit! Let's take a break for a second and see what just happened. Go into the home folder on your computer and look at the Hello-World folder or look at whatever folder you're using for a local repository.

What you won't see is a. Git hides it in there, but because you ran the git init command you know it exists. It doesn't, and you have to tell it. This command will do the trick:. If you want to add other files to commit, you'll use the same command but replace README with the name of a different file.

Now, run this command to commit it:. While the other commands were pretty straightforward, the commit command has a little more going on so let's break it down. See for some discussion about this. I would really appreciate to be able to download the older version compatible with OSX The updater tries to elevate privileges and claims to want to install a 'helper'.

I found the update info here: There seems to be a lot of misinterpreting this update. This is less a sign of it still being available , and more a message to get off the old unsupported version and update to the new version.

In the morning, reelsense! Awesome that you are keeping classic alive! It's much better at highlighting the inline diffs: Very happy to discover that classic is still available! There's several issues with the new one, many of which are already mentioned here but also the fact that it the classic one seems to rebase on pull automatically as well and the fact this isn't even being considered anytime soon according to response on I just did 2 weeks on the new desktop app and am now back on Classic.

I gave it a real try, I really did but the timeline view has proven to be too much for me to give up. Indeed, and the unwillingness to help by the maintainers, who introduced the problem by silently making he old version incompatible with the OS where it previously perfectly worked, is more than sad.

I assure you we have not done anything to deliberately make the old Desktop for Mac incompatible with new OSs. We stopped development of that app almost 2 years ago, so OS updates are more likely to be the reason the old client doesn't work on your OS any longer.

We do have others who have stuck around with the older clients, so I'm not confident saying it doesn't work on the current crop of OSs that are out. One plus side of the new app is that it now works on some Linux distros. The update has the version restriction that blocks any installation attempts on the same OS. It did work earlier, so that restriction must have been changed. But the only way to know the truth about what was really introduced is to have both versions to compare.

In fact, having the old version simply available would make this whole discussion unnecessary. So many software makers leave their legacy products available with no warranty and no one had any problems with that ever.

Would it be too much to ask Github to follow that friendlier route instead of unnecessarily alienating its users? The new native. Enjoy your latte. I tried GitKraken about 2 years ago. Is it any better these days? I think I have enough ;-. I'm having a pretty flawless experience so far, and cross-platform too. For me the fork and merge workflow is really valuable and things like getting up to date with upstream branches are really easy to do.

These are the areas where GitHub Desktop did well before the major update. Cookie Settings. Learn why people trust wikiHow. Download Article Explore this Article Steps. Related Articles. Article Summary. You can use any web browser to download files. Use the search bar at the top of the page to find the file you want to download and the results will list repositories that match your search.

You'll see this option on the right side of the browser. Once you click Releases , you can click to download the installer or the source code.

If there is no Releases available, continue following these steps to download a file. You'll see this above the list of files within this repository next to a button to download all the files.

It'll open within GitHub in your web browser. You'll see this next to Blame and a monitor icon above the space where the file displays. Your file manager will open so you can select a name and location to save the file.