2 months ago, I travelled to Vienna, Austria, to attend WordCamp Europe – my favourite conference in the world! It’s such a huge event and a great opportunity to catch up with old friends as well as making new ones. At WordCamp Europe, Matt Geri did a talk on “The Ultimate WordPress Development Environment”, including using WP Pusher for deployment.
Last week I wrote a guest post over on the WP Tavern about how fundamental Git is for WordPress teams. In the post, I mention 3 signs that will make it obvious to me that your WordPress development team is not in fact working as a team – but rather as small 1-man teams. The 3 signs are:
- Lack of version control
- Lack of a code collaboration platform
- Lack of a deployment strategy
Git is a fundamental enabler of team work, so without it, it’s hard to get to step 2 and 3 in that list. If you want to read the article, check it out over on WP Tavern.
Pull requests are an essential part of code collaboration. In this blog post, I will show you why and how I use pull requests as a core part of my workflow.
In this short screencast, I will show you how you can use WP Migrate DB Pro together with WP Pusher to improve your workflow.
Composer has truly revolutionised the PHP world and made it a better place. For WordPress developers, Composer is tempting, but doesn’t change the fact that WordPress doesn’t have a proper way to manage 3rd party dependencies.
When you use Git in your WordPress deployment flow, there is a special configuration file you should be aware of.
.gitattributes can drastically clean up your plugins and themes for end users. Follow along and I will show you how simple it is to use.
This is the story about how I wasted 3 days, but also, which is more important, how I set up continuous integration for WP Pusher with CircleCi. With a continuous integration service, you can have your tests run on every commit and ensure that nothing is broken. That is, if you have some tests to run of course.
Composer seems to be something everyone is talking about in the WordPress community these days. It is a great tool for developer productivity and code reuse. However, if you are trying to use Composer to distribute your WordPress product to end users, you might be doing it wrong ™.
During the beta testing of WP Pusher, I have seen numerous examples as to how WordPress developers use Git to manage their projects. WP Pusher is opinionated in terms of how your Git setup needs to look, in order to use the service. In this post, I will try to explain why.
These days, I’m working on the plugin that makes WP Pusher update themes and plugins directly from GitHub. Having been away from serious WordPress development for quite a while, I thought it would be interesting to highlight a few of the approaches I have been using during the development of the plugin.