How do I get local files to reflect a specific commit point?

[Bledig]

I just set up a repo to use with Unity, Sourcetree as the git client. Something I'm not clear on is testing Unity at different commit points. So for example, a separate branch is created for a sprint, someone else makes changes, does a commit, and it needs to be tested on my end. I'm expecting in Sourcetree that I can select that point, perhaps in history, and then the files locally will change to reflect that snapshot. So then I could just launch Unity for that project and it can only access the files that were available at that particular commit. Am I understanding the concept correctly? And how do I do that?

The concept is using only one installation of Unity, one repo, but able to test at any point, in any branch, along the development process. Thanks.

[Mikael Sandberg · Accepted solution]

Hi @Bledig,

Welcome to Atlassian Community!

To checkout a specific commit, locate it in the History view, right-click and either create a branch or checkout the commit. If you need to come back to the commit multiple times I would recommend that you create a branch. 

[Bledig]

I like it! It works well, thank you.  :)

[Jeff Tillwick]

Yeah, just scroll through potentially thousands for commits manually and find the matching commit id you have already copy and pasted. SO EFFICIENT. Why would you ever need a UI element to checkout by commit id? That would be too simple. The hunt is more important. /s 

How about a solution for those of us that live in the real world?

[Jeff Tillwick]

The best way I have found is to create a new branch from that commit. Press the branch button in the top button bar and give your branch a name and select `Specified Commit:` and put in the id.