Git and the command line can be a daunting prospect, luckily there are multiple Git GUIs, which work across a variety of platforms such as, OSX, Windows, and Linux.
Push-to-Deploy is the feature of WP Pusher that will keep your WordPress websites up-to-date every time you push some fresh code to your Git repositories. In this post, we are going to take a look at what Push-to-Deploy is, how best to use it for an effective workflow.
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.
As part of the Git for WordPress video course, Danny van Kooten shows how he uses Git to release a new version of his plugin MailChimp for WordPress.
Danny van Kooten is the founder of Ibericode and the creator of MailChimp for WordPress, one of the most popular WordPress plugins on WordPress.org. I have known Danny for a while and I know he has a pretty solid workflow, so I reached out and asked if he would like to share it, which he agreed to. Thank you, Danny!
I think it is fair to say that pull requests were made popular by GitHub and their brilliant implementation of the concept. Used in a strategic way, pull requests are a very powerful collaboration tool to have in your toolbelt – especially if you work in a team.
According to OSS Watch, a pull request “is a method of submitting contributions to an open development project“. But a pull request can be more than that. If you really adapt pull requests into your workflow, they provide a great space for teams to communicate, collaborate, educate and onboard new team members. This is now the norm in most open source projects, but many development teams – especially in the WordPress sphere – are not even using Git yet. If your team have not yet adapted Git (or another version control system) into their workflow, they are simply lacking the most basics of collaboration tools. The abillity to discuss and review code changes in a pull request is just one of many reasons to use Git, but it is definitely one that is big enough on its own.
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.
The WordPress world, once dominated by Subversion, mainly due to the infrastructure of WordPress.org, is slowly moving towards using Git. This is great news, but for many developers Git can seem strange or even intimidating. In this post I will do my best to demystify Git for WordPress developers.