The bottom-left panel shows all the changes you haven't added to the repository. The window in GitX should look something like this screenshot. The left side is the "Browse" mode, the right side is the "Commit" mode. The toolbar contains a two segment "View" button. gitignore file, save it to ~/.gitignore and run the following in the Terminal:Īll files for tracking the repository are kept at the top-level of the repository (unlike older version control systems like svn or cvs which littered files in every directory). If you did want to set this up as a global. This doesn't work for me unless I remove the question mark. gitignore file contains the line ".DS_Store?". gitigore file set up, then you'll probably want to add the content of this file to your. rename from the Terminal or save from Xcode or TextEdit). Since you can't rename files to start with a "." in the Finder, you'll need to set the name using another program (i.e. You will need to save this file with the name ".gitignore" in the top level folder of your new Xcode project. This will tell git to ignore build products and Xcode user-settings files that you don't really need to commit into your repository. Gives a ".gitignore" file suitable for use with Xcode. To do this correctly involves the following three steps. Making your project into a git repositoryĪs soon as you've created your Xcode project from the template, the next step should be creating the repository. I consider the Xcode 3 version control integration to be worse than the command-line because it simply isn't informative or robust enough. Of course, this doesn't mean that all graphical user-interfaces are always better than the underlying command-line. GitX is a good example of how a program can improve upon the information structure available on the command-line: it shows nice graphical diffs whenever you're browsing the repository or committing new changes, making browsing and committing much faster and easier. I've discussed this before but I consider the command-line and a terminal window a poor way of gathering structured information and getting feedback about multi-part tasks. I prefer to use GitX instead of git on the command-line where possible.
email replace "My name in git" and with the name and email address you want to use. name "My name in git" git config - global user. Do this by opening the terminal and running the following commands: Once that's done, you should set your username and email address (these will be tagged on all changes you make). Installationĭownload the git installer (as I write this, the current version is 1.7.3.3).
Gitx bug list mac#
There are also some good tools around which make git use on the Mac more enjoyable - particularly GitX. The advantage with git is really that it's enjoying a lot of popularity at the moment and that popularity means there's plenty of documentation and how-to guides around to help out if you get lost. Most modern, distributed, version control systems share a pretty similar feature and command set. I recommend you use git for version control.
Gitx bug list code#
Version control systems protect your work, help you review what you've done, help you share code if needed, work like a massive undo buffer when necessary and can help you keep your code tidy.
Gitx bug list how to#
In this post, I'll take a quick look at how to keep your projects in git and how to manage that easily on the Mac.
0 kommentar(er)
