Speeding Up My WordPress Workflow Using Git

I’ve started working with Git as part of my Web development workflow, and am just getting the hang of some of the tools. I’m still running into problems, but it’s mainly where I haven’t taken the time to read Pro Git and learn what it is I’m trying to do.

Here’s a quick overview:

  • make changes in code
  • test in local development server
  • commit changes to git repository
    • git add .
    • git commit -m “Explanation of changes.”
    • git push
  • move updated files to external dev server
  • test on external dev/staging server to verify changes
  • move to production site (on same server as dev/staging)
  • verify changes on production. smile at work accomplished

I’ve also tried working with git flow for feature and release management, but haven’t quite got the hang of it yet to make sure I’m doing it right. Once I know more about what it’s doing, I’ll write about how I’m integrating it with my own workflow.

Best Practices for Git Commits?

I’ve been updating my online portfolio hosted on GitHub, and find myself getting lazy. Instead of developing on my local server, then publishing changes, I’ve been making little changes and pushing them to the portfolio repository. Sometimes it’s as simple as adding a link, other times it’s adding/removing a feature, or a whole group of images at once.

I get the feeling there’s a better way of committing and pushing changes in general, but before I get too entangled in one method, I thought I’d ask you who are working with Git (or any versioning system, for that matter) how you do things. Any advice is welcome, especially if you have a particular reason for how you work.