I’ve spent most of this week talking about business. But today I really wanted to share a cool tool with you. If you’re a fan of using Git on the command line you’ll love this. I’m going to show you how to use git bisect to find bugs. It will help you narrow down when exactly a bug was created.
You’ll find this very helpful when you start working on repositories that have hundreds of contributors (WooCommerce has more than 300!). Many times it’s hard to figure out exactly when a bug was created and with hundreds of commits between releases it’s critical you know how to go through them quickly.
Writing plugins for yourself or others is a natural step for a developer that uses WordPress. Unfortunately if you want to share your plugins with the WordPress community that means submitting them to the WordPress plugin repository and there is one really sucky part about that – learning Subversion.
Subversion, or SVN, was great years ago when Git didn’t exist. But since the emergence of GitHub, Git has become hugely popular and produces far fewer headaches than SVN. As a result new developers don’t even bother learning SVN. Why learn to drive a stick shift when you can drive an automatic that has better gas mileage and more control?
With a lot of googling and several hacking sessions I took an existing shell script and modified it so that is does all of the cumbersome SVN for you. It will pull down the latest version of your Git repo, reproduce it in SVN, and push the changes to the WordPress plugin repository. It will even move your plugin assets (including the header image and screenshots) to the appropriate spot in the SVN repo.