How are we currently solving all these flaws in our development environments? Often it looks like this: Build everything locally with Grunt, Gulp, Webpack, Composer etc. and copy / paste it via FTP. Good luck doing that on a team! This is not how these tools were imagined. Quick aside: This is still a big improvement to the previous WordPress way of just reinventing the wheel every. single. time (Hello, security issues!).
For 3 years I have been working to improve the workflows of WordPress developers with WP Pusher (a Git tool for WordPress) and now I’m working on a much more comprehensive solution.
3 years ago I launched a side project called WP Pusher, a plugin that allows you to install and update plugins and themes from a Git repository. WP Pusher can automatically make sure your site is up to date every time you push a change to GitHub or Bitbucket. Even though the plugin was banned from the w.org directory, it has managed to get a lot of attention. Today some teams are using WP Pusher on hundreds of WordPress sites.
WP Pusher is only a small step towards a better world for WordPress developers. It takes FTP clients out of the equation (can I get a “yay!”?). My experiences from working with Laravel PHP, and before that Ruby on Rails, are what prompted me to make Git more accessible and useful to WordPress developers. However, I still have a feeling that there is more I can do.
Working on WP Pusher and talking to hundreds, if not thousands, of people about their struggles with workflow has given me a lot of insights. That is why I have decided to tackle a larger part of the problem and decided to build Branch.