#Using sourcetree to backup my projects for free
#Using sourcetree to backup my projects software
#Using sourcetree to backup my projects code

If your changes have been staged, but not committed: You should use the command git restore -staged -worktree FILENAME.HERE.

If your changes have not been staged or committed: The command you should use in this scenario is git restore FILENAME.HERE.

Here is what you should do for each scenario: Changes that fall in between these two extremes-i.e, you've staged them but haven't yet committed them-must be handled with a slightly modified 'git restore' operation instead.

#Using sourcetree to backup my projects code

If your code changes have not been staged yet, then you can use git restore, whereas' `it checkout` will be necessary if changes have been committed. Each option can be handled via a special command, but the exact option you should use depends on the state that your project is in when you first realize a file needs to be restored. In Git, there are multiple ways to restore lost files. Here are the three methods you should consider using when your project's files go missing: 1. Choosing the perfect file restoration process comes down to working with whatever combination of IT infrastructure and tooling you currently have. Similarly, a command-line-based approach can't always be used either. For instance, there's a method that might be better for those using GitHub, but it isn't an option for those who aren't. The method you choose to work with depends mainly on the tools you have at your disposal.

Git restore deleted files with 3 different methodsĭeleted files may be a troubling issue to come across in your repository, but they can thankfully be restored using any one of three different methods.

You'll have no problem being able to git restore deleted files using the information covered below. We'll describe the details involved in bringing missing files back from the grave in this article and touch on how you can do this. Thankfully, Git offers some simple solutions that you can use whenever you need to.

#Using sourcetree to backup my projects software

Voilà: you now have a new branch named 'old-project-state' reflecting the old version of your project - without touching or even removing any other commits or branches.Git is a great way to track and control the development of any type of software project, but issues like accidentally deleted files can quickly make for major headaches in your workflow. If you don't want it to start at the current HEAD revision, you also need to provide a commit hash - the old project revision we want to restore. However, providing the -b parameter, you can also let it create a new branch (named 'old-project-state' in this example). Normally, the checkout command is used to just switch branches. Since 'branches' are so cheap and easy in Git, we can easily create a new branch which starts at that old revision: $ git checkout -b old-project-state 0ad5a7a6 However, there is also a 'safer' way in case you'd prefer leaving your current HEAD branch untouched. If you're sure that this is what you want, everything is fine. And in case you made a mistake: simply hit CMD+Z to undo the reset and restore the removed commits! Restoring a Revision in a New Local BranchĪs said, using the reset command on your HEAD branch is a quite drastic action: it will remove any commits (on this branch) that came after the specified revision. In case you are using the Tower Git client, you can use the reset command right from a commit's contextual menu. You'll be left with a couple of changes in your working copy and can then decide what to do with them. If you use it instead of -hard, Git will keep all the changes in those 'undone' commits as local modifications: $ git reset -soft 0ad5a7a6 The reset command comes with a couple of options, one of the more interesting ones being the '-soft' flag. All commits that came after this version are effectively undone your project is exactly as it was at that point in time. This will rewind your HEAD branch to the specified version. The fastest way to restore an old version is to use the 'reset' command: $ git reset -hard 0ad5a7a6

#Using sourcetree to backup my projects for free

Download Now for Free Returning to an Old Revision