![]() 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). 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. 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. I'll show you how it will help you as a solo developer, even if you don't need many of the traditional features of a version control system.You can avoid the (often cryptic) command-line for most tasks. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |