Proofing More than One Branch in a Single Environment With no single body of proofers, I can wind up with code sitting in one environment or the other while local bureaucracy and revisions play out. Beyond this, often there are multiple stakeholders who will need to rigorously proof and vet changes some of those changes are subject to strictly enforced government standards. This means I've been known to juggle multiple branches in either Development or Staging. There are times when I will get absolutely battered with code-change requests, often with no clear timeline between development and go-live. It can be a non-traditional workflow at times, but given the pace of code changes on my client's site, locking Stage into a proofing ground is often counter productive. I branch out for projects requiring code changes and, due to client needs, often find that Staging is really just another environment for development (as opposed to being a QA/proofing ground) I avoid relying on it solely for development (I try to keep it clean enough to drop a production database into whenever necessary), but sometimes there's no way around it. I follow a couple of basic principles in my workflow: the master branch is kept as clean as possible so that it can be pushed to Production at any given time. Additionally, I run a Localhost environment, and have even been known to rely on Virtual environments, such as the one I recently setup for Drupal 9 testing. I usually work with a Production, Staging and Development environment. I have a feeling, though, that a lot of devs (myself included) invest so much of their bandwidth on work that workflow takes a back seat. Lastly, I'm gonna assume that this isn't the first time this technique has been employed or written about on the internet-it's probably a no-brainer for more experienced Git users. ![]() You've got a little experience with environments. ![]() You've got a basic understanding of Git and branches.You're not entirely new to workflow management.Before I dive hard into the meat of this post, let's get some basic assumptions out of the way-I'm gonna assume that:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |