An example of this would be a pre-commit hook, that you could use to prevent a commit from happening according to some custom criteria.Īll hooks are simple executable files, and can be written in whatever way you want to. githooks(5)Įvery time Git does something, you usually have the option of taking an action before or after Git has done its bit. You can also use this file to specify which end-of-line conversions Git should perform for certain file types, or files that it should treat as binary files. And we won’t ever have to manually merge schema.rb again. This tells Git than whenever it is merging db/schema.rb, it should use our custom merge strategy instead of the default one. Any file (and directory) matched by these globs won’t show up in git status, and if you try to add them via git add, Git will refuse to do so (you can still add them by specifying the -f flag when adding).įor example, Rails 3 projects use the following. Placed at the root of the repository, it contains glob patterns specifying all the files you want Git to ignore. However, they will still show up whenever you type git status, even though they are purely noise at that point.įor this reason you can specify what files you want Git to ignore in a special file called.
#GITX WONT INSTALL CODE#
Things like temporary files, logs, configurations that are specific to a computer, files that are for testing only, private keys for code signing or files that can be easily regenerated all don’t belong in your repository. You don’t want to commit all your files into your repository. So you can customize all these settings for each of your repository to your liking, just run the git config command in your repository without the -global flag. The reason for that is that Git not only looks at your global gitconfig (located at ~/.gitconfig), but also a repository-specific config (. Now, you’ll notice that for each and every git config I used the -global option. Simply add the following to your ~/.bashrc:
#GITX WONT INSTALL INSTALL#
Luckily, enabling the Git completion for both Bash and Zsh is quite easy if you used Homebrew to install Git. I use Git primarily from the command line. The Git Homepage lists quite a few introductions, tutorials, guides as well as online books that can help you out. On the web, there are a few more options. They are more thorough, but aren’t for the faint of heart either. The fastest way to get to them is by typing git help, and git will open them for you. The second one is having a look at the manpages themselves. The first one is typing git -h (replacing with the command in question of course), and Git will print a short overview of the call syntax as well as the most important options for you. There are basically two ways on the command line. No matter what you’re doing with Git, there’s always some kind of documentation that can help you out. I also assume you have basic knowledge of the command line. Warning: Some of these tricks and tips are specific to my setup (Mac OS X Snow Leopard, Git 1.7.4) and workflow(s), and might not quite work for you as described. You can find most of these things in my dotfiles repo, as well with a lot of other stuff, like parts of my Zsh config. It is an annotated tour of my Git config, Git related scripts and commands, and various other tips and tricks I picked up over the years. This post is based on a talk I gave at the 18th Cocoaheads Meetup Vienna (CHW018) on Feb 17th, 2011. Note: A german translation is available here A few of my Git tricks, tips and workflows
0 kommentar(er)
