Earlier, I wrote about a way to import an exisiting git project into bitbucket. I’ve since discovered a much easier way to do this using git’s own commands. Instead of having to use git’s daemon mode and have bitbucket import your repository, you should setup a new bitbucket repository and push to it. Assume you […]
When bitbucket added git to their code hosting service, I signed up to try out the service. Primarily since they offer unlimited free private repositories, which is perfect for one-coder projects like this blog. Each repository also gets a wiki and an issue tracker. Creating an account was straight forward, I then had to import
I can’t seem to remember the specicfic magic git switches when pushing and pulling branches between different git repositories, so I am writing it down here. 1. Create your local branch for development git checkout -b my-branch 2. Push local branch to remote server & track it. git push -u origin my-branch 3. Checkout and
Are you still using SVN but have some users clamoring to try out git? Kris.me.uk details all the commands and workflow to make it work. While I’ve known that git had some svn integration available, I prefered to switch cold-turkey to git. You can read the reasons I switched to git. This article looks at
Clone … What could possibly go wrong? If you’re a coder, you’ve already heard about distributed version control systems (DVCS) and git in particular. I was content, almost complacent, in my usage of subversion to manage my source code, both for personal projects and at work. Subversion was intended as a “compelling” upgrade for CVS,
This post describes a small tweak to make to php lint checking via a git pre-commit hook. Using git hooks to check syntax errors – Tim Akinbo’s Blog
THOUGHTS Drupal Development and Deployment using Git | ruzee.com – Steffen Rusitschka
Jow Maller outlines a straightforward system for using git to manage code from development copies and branches through production. The fact that deployment to live is automated, but I’d be worried about broken or unreviewed code getting deployed unintentionally. I think the best way to prevent that is to have live be its own branch,