Reviewing code is a great habit to get into. Code reviews help share knowledge between your team members and help catch bugs before they get into production. But how do you get into the habit of reviewing and avoid the we don’t have time to do this mentality? Visual Studio Team Services (VSTS) has some great options...

I created my GitHub account in August 2010, lets look at what I have done with it. In 2010 I started by committing the code for an old php website I had created. Then in December I committed some other php sites. Between 12 December 2010 and 29 September 2011 I must have created some automated process which is why...

One of the features of git is the ability to tag a point in my change history with a tag. For a while now I have been manually tagging my code whenever I do a release, so I can easily work out what has changed by doing a diff between two tags. Now that I am automating my release process with TeamCity I am thinking...

Today I did a clone of one of my git repositories and it took ages to download. Looking into what got downloaded it was easy to see why. The .git folder was over 500Mb in size. I know how this has happened. This repository was created in 2013 and has been used by me as a dumping ground for lots of things related to the...

I use git as my source control system. Here are some of the most common git commands in no particular order. Check Out a git Repository git clone /path/to/repository Add files to commit git add Commit files to git git commit -m “Commit message” Push changes to server git push origin master Show status git status...

Writing better Git commit messages

I always use source control for my coding changes, however some of my commit messages leave something to be desired. I always try to write a commit message but I often think that the change themselves should be enough to indicate what I did. I also don’t need to include who made the change or the time and date and that...