Don Thorp's Library tagged git →  View Popular, Search in Google

"[Basic Repository] commands are needed by people who have a repository --- that is everybody, because every working tree of git is a repository.

In addition, [Individual Developer (Standalone)] commands are essential for anybody who makes a commit, even for somebody who works alone.

If you work with other people, you will need commands listed in the [Individual Developer (Participant)] section as well.

People who play the [Integrator] role need to learn some more commands in addition to the above.

[Repository Administration] commands are for system administrators who are responsible for the care and feeding of git repositories."

git howto

git development

TicGit is a simple ticketing system, roughly similar to the Lighthouse model, that is based in git. It provides a command line client that uses the ‘git’ gem to keep its ticketing information in a separate branch (called ‘ticgit’) within your existing git repository. All the data is file based and rarely changing, decreasing the likelihood of a merge issue. Right now, ticket branch merges need to be done manually and separately, but I’ll write a tool that helps pretty soon.

git issue tracking

git version_control development

Using GitHub almost requires the use of ssh to access repositories securely. It is absolutely required to update repositories. Unfortunately, that can run afoul of the “IT overlords” in many corporate environments. At my workplace, a Microsoft ISA authenticating web proxy server is in place, restricting most outbound traffic. Specifically, port 22, the ssh port, is not allowed and that means I can’t pull or push to my repositories on GitHub. I’m sure I’m not the only one in this situation.

However, if your proxy allows SSL connections (e.g., for banking, etc.) then there is a way around the problem. An SSL connection is meant to be encrypted and should be opaque to your proxy. What that means is the proxy has to allow direct connections in some circumstances and that opens the door for accessing your GitHub repositories from behind the firewall.

git firewall

This is the website for the Pro Git book, written by Scott Chacon and published by Apress. Here you can find the full content of the book, a blog with tips and updates about Git and the book and open source projects related to Git or referenced in the book. Read the book now!

git

Git Bundle

You may have read that a lot of prominent people have recently moved to Git and are loving it. I too am one of those who fancy this new kid on the block but never got very far with the bundle I started for it.

Fortunately Tim Harper recently picked up on my initial efforts and has done a great job at not only making this bundle functional but also downright impressive :)

The much improved Git bundle can be found at Gitorious and discussion about it can be directed to its Google Group.

git textmate

git config branch.autosetupmerge true

git

Git is a distributed version control system so it allows you to create branches locally and commit against them. It also supports a more centralized repository model. When using a centralized repository you can push changes to it so that others can pull them more easily. I have a tendency to work on multiple computers. Because of this, I like to use a centralized repository to track the branches as I work on them. That way no matter what machine I’m on, I can still get at my branches

git

Checking out remote branches, deleting them, and publishing new ones is part of most Git users’ daily workflow. But seriously, who wants to type that much? I certainly don’t, and you shouldn’t have to either.

Enter git_remote_branch, a helpful RubyGem for just this task. It installs a new executable to help take some of the chore of working with remotes away. Here are some of the commands it has:

grb create branch_name [origin_server]

grb publish branch_name [origin_server]

grb rename branch_name [origin_server]

grb delete branch_name [origin_server]

grb track branch_name [origin_server]

What’s awesome about it is that it shows what Git commands are running underneath it, so it’s quite easy to figure out exactly what’s going on.

git ruby gem

One of the first real points of frustration a developer encounters with Git is the initial unresolved merge conflict. And it’s only a matter of when and not if it’ll happen.

git howto

Host github.com User git Port 22 Hostname github.com IdentityFile ~/.ssh/id_dsa TCPKeepAlive yes IdentitiesOnly yes

git ssh github