- Set up p4merge how to#
- Set up p4merge install#
- Set up p4merge software#
- Set up p4merge code#
- Set up p4merge windows#
Staged Change A change that someone has told Git to pay attention to when it commits. It will then show me all the unstaged and staged changes. To do that I find it easiest to open the Git GUI application, hit ‘open existing repository’ and point it at the root directory of local repository. When you have made changes you are happy with and want to persist them there are several steps you have to go through.įirst, you want to commit those changes on your local repository. Understanding how branching works, how it deals with changes, etc. Again, PLEASE read the section in the book on branching. (You can also check out staging as another play mechanism)īUT BE CAREFUL! I can’t tell you how many times I screwed things up because I didn’t realize I was on some branch other than my main one. But if you want to play around with something potentially messy it is often much easier to just create a branch and play there. Most folks (including Thali) keep Master as the main branch. Having read that section you understanding that ‘master’ is the default main branch in all Git repositories. If you don’t understand how Git handles branching then, to be honest, you’re doomed. Go back to the Git book and re-read the section on branching. What the previous command did was tell your local repository that there is another repository it will know as ‘upstream’ (this is the traditional name, just like ‘origin’ is the traditional name for your forked repository). Open up the Git Bash shell, navigate to the root of your local repository and type in: To enable that we need to tell your local repository about the master repository. It calls your forked repository ‘origin’.īut what about the master repository? As we’ll discuss below there are times you will need to pull down changes from it. When you cloned your forked repository on your dev box Git understood it was a clone and automatically set up the identity of the forked repository. Forked Repository This is the repository you created by forking the master repository, it starts off as a clone of the master repository Cloned (or local) Repository This is the repository you created on your dev machine, it starts off as a clone of the forked repository Master Repository This is the repository that contains the actual Thali code. There are now three repositories you care about. Now cd into that directory and you are in your own personal depot! This will automatically create a sub-directory whose name is equal to the last part of the path in the URL you copied.
Set up p4merge windows#
Then open up your favorite Git client (on Windows I do this from Git Bash shell) and type in: git clone In your forked project, click on the clone button and copy the https URL there. To do real work however you will need to create a local clone of your forked repository on your dev machine. You are now in your new home for doing your work. Give it some pithy name and a description and hit save. So once you know which of our repositories you need to play with go to their links in codeplex and click on ‘source code’ and ‘fork’ and select ‘create new fork’.
Set up p4merge code#
Fork!įor lots of reasons I’m happy to discuss we want our developers to fork their own version of the code and work there. You have to follow the instructions here to get it to work again.
Set up p4merge install#
However a problem is that git gui won’t “just work” after install for some reason.
I use the same Git Client as for Windows. If you need to mess around with files directly you can just use the explorer. Honestly I would just focus on ‘cd’ and ‘ls’. ‘del’ won’t work, you need to use ‘rm’, etc. So, for example, let’s say you want to navigate to c:\temp. But this shell really wants to think it’s in UNIX land, not Windows. In most cases it’s easiest (with a few exceptions I’ll mention later) to use the Git Bash shell. I use the default options when installing.
Set up p4merge software#
Software Windowsįor Windows I use the Git Client. So please treat this guide as more along the lines of hints and pointers.
Set up p4merge how to#
So, for example, it’s pretty much impossible to write a short guide to how to handle basic Git commands for Thali because Git’s power means that all sorts of things can go wrong. The unfortunate consequence of this power is that easy things are, in my opinion, hard.