Putting your source code under version control with Git is strongly recommended, not only because it’s nearly a universal practice in the Rails world, but also because it will allow you to share your code more easily (Section 1.3.4) and deploy your application right here in the first chapter (Section 1.4).
(Link: Ruby on Rails Tutorial: Version control with Git)
Uncategorized
repo.or.cz is a public Git hosting site. Create a project in a snap, publish your development, give others push access and let anyone have a look and contribute. Alternatively, if you just see a random git:// URL fly by and want to check it out, or you have limited bandwidth or want backup – just quickly set up a mirror of any project published elsewhere and we will provide pull and gitweb access for the project, or send you notifications when new stuff gets committed. (read more, terms of use) (want to help?)
(Link: repo.or.cz – Public Git Hosting)
Uncategorized
Unlimited Repositories
Unlimited Trac Projects
Unlimited Users
Custom Domains
Custom Logos & Colors
SSL Secured
WebDAV Shared Drives
Scheduled Backups
2GB Storage
$1/GB Additional Storage
(Link: Repository Hosting – Subversion Hosting, Git Hosting and Trac Hosting)
Uncategorized
toto is a git-powered, minimalist blog engine for the hackers of Oz. The engine weighs around ~230 sloc at its worst. There is no toto client, at least for now; everything goes through git.
(Link: toto is a git-powered, minimalist blog engine for the hackers of Oz)
Uncategorized
A project is always more fun when you’ve got friends working with you, but how can do it when working on a coding project? I’ll keep my keyboard to myself, thanks.
Enter GitHub. With this web service, you can share your coding projects and collaborate with ease!
(Link: Getting the Hang of GitHub | Nettuts+)
Uncategorized
Table of Contents
* Feature Development
* Bug Fixes
* QA Branch Management
* Production Tagging
* Summary
* Notes
(Link: ReinH — A Git Workflow for Agile Teams)
Uncategorized
git-wtf displays the state of your repository in a readable, easy-to-scan format. It’s useful for getting a summary of how a branch relates to a remote server, and for wrangling many topic branches. git-wtf can show you: – How a branch relates to the remote repo, if it’s a tracking branch. – How a branch relates to integration branches, if it’s a feature branch. – How a branch relates to the feature branches, if it’s an integration branch.
(Link: git-wtf – displays the state of your repository in a readable, easy-to-scan format)
Uncategorized
In today’s tutorial, we’ll learn the basics of what might possibly be the best VCS in the world: Git.
(Link: Easy Version Control with Git – Nettuts+)
Uncategorized
Forget everthing you know about branches. Your knowledge of what a ‘branch’ means in Subversion is poisonous, especially if you internalized it pre-1.5, like I did, before Subversion finally grew some basic merge tracking capabilities. Forget how painful it was to merge, forget how long it took to switch branches, forget how impossible it was to merge from a branch more than once – Git gives you a whole new world when it comes to branching and merging.
(Link: Why You Should Switch from Subversion to Git)
Uncategorized
The Git Textmate Bundle. Version 1.6.5 (released July 24, 2008)
(Link: Git Textmate Bundle – Gitorious)
Uncategorized
The VCS you have constructed is now a reasonable facsimile of Git. The main difference is that Git gives you very nice command lines tools to handle such things as creating new snapshots and switching to old ones (Git uses the term “commit” instead of “snapshot”), tracing history, keeping branch tips up-to-date, fetching changes from other people, merging and diffing branches, and hundreds of other common (and not-so-common tasks).
As you continue to learn Git, keep this parable in mind.
(Link: The Git Parable)
Uncategorized
Understanding Git Conceptually
The conclusion I draw from this is that you can only really use Git if you understand how Git works. Merely memorizing which commands you should run at what times will work in the short run, but it’s only a matter of time before you get stuck or, worse, break something.
Half of the existing resources on Git, unfortunately, take just that approach: they walk you through which commands to run when, and expect that you should do fine if you just mimic those commands. The other half does go through all the concepts, but from what I have seen, they explain Git in a manner that assumes you already understand how Git works.
Intro to Git for Web Designers
Unless you’re a one person web shop with no team to collaborate with, you’ve experienced the frustration that goes along with file sharing. No matter how hard you try, when multiple people are working on a single project without a version control system in place things get chaotic.
If you work with developers on the buildout and implementation of websites, the merge between front-end templates and back-end functionality can be a scary black hole
Git/Github survival guide | Ivan Porto Carrero
Lately I’ve been helping a few people to get started on Github. I use git at the command line and my survival guide is also based on that way of interacting with Git. So I thought I’d write the procedure up so that I can just point people to this page.
