Because GitHub didn’t offer private repositories when the plugin was first built, the code was initially split between GitHub and BitBucket. After GitHub was acquired by Microsoft, they started offering free private repositories on all accounts, which made transitioning a no brainer.
We created a Kanban for WordPress
organization on GitHub so that all the code could live under one roof. This makes it easier to onboard anyone anyone who would potentially work on the plugin without having to give them access to every individual repository.
In addition, this gives us access to the very powerful piece of infrastructure known as GitHub Actions. For the non-developers in the crowd, GitHub Actions allows you to automate certain things about your code. In our case, whenever we tell GitHub that we’ve created a new version of the plugin. GitHub Actions automatically pushes a new update to the WordPress plugin repository.
On the side of deployments, I’m a big believer in making them as painless as possible. With some of my other plugins, I don’t deploy updates as often as I should because I don’t want to mess with SVN, and I wanted Kanban WP to be different. So as of now, with the help of the wonderful folks at 10up
, all of the plugins are set up to auto-deploy updates . This means I can use the git workflow I’m accustomed to with all of my other projects, and work totally within GitHub, which is a huge win.
There’s going to be further consolidation in the future as we bring the integration plugins into the main plugin itself. But for now, I’m happy to have one less account, with everything organized under one roof and all the automation I could want.
Another upside of this is that we can easily make updates to our plugin readme file, as well as the header images and screenshots that are displayed on the plugin repository, which leads us to…