Tony Rasmussen's Blog

The slowest, most tedious way of finding a bad git commit is something we've all done before. You checkout some old commit, make sure the broken code isn't there, then checkout a slightly newer commit, check again, and repeat over and over until you find the flawed commit. Using git bisect is a much better way. It's like a little wizard that walks you through recent commits, asks you if they are good or bad, and narrows down the broken commit. In this blog post, I encourage you to create a fresh git repository and walk through each step. Hopefully, you'll gain an intrinsic understanding of git bisect by the end of the exercise. Read More…

Over the years, I've created a list of ways to make Drupal easier for one of my target audiences: the non-technical admins and editors that run the day-to-day operations of a website. My list is getting huge, but the following six ideas are always reliable. Read More…