Git
Over the last few months I have seen several discussions by many developers - especially in the CodeIgniter community - about wether or not to convert their GitHub repo's over to BitBucket. I say: why not use both?
Use Git to deploy your web applications without having to faff with FTP syncronisation or manually working out which files need to be uploaded.
Stable and unstable branches mean that while you work on a new version of your software, you maintain the current version by working on bug-fixes and small tweaks. Find out how to achieve this using Git.
We've all done it. Started working on a task, ticket or issue and realised we have forgotten to create a branch. Using git stash we can easily hide these changes, create a branch and then get the changes back.
I have been using Subversion for years and have come to know it like the back of my hand. Recently I began using Git and it was a much trickier transition than I had expected. Now I have finally found my feet with the basics of Git I thought I should take the time to explain my main points of confusion during the learning stage and give you a few things to look out for.
I have finally joined GitHub and I am pretty happy about the decision. It seemed like a bit of a silly fad at the start but it is definitely more than that and for me, solved a few problems in one. Mainly, how to run multiple projects based on one code-base without being stuck in the same repo; I'm looking at you SVN.
