This is all great and I’m all for any process that makes it easy to rollback in case of a blow up. But my question is what would you do if you have a client that you work on their site from time to time, but they also work on it. The caveat here is that they don’t have any knowledge of source control and just make changes on the fly.
Would you “sync” their changes each time you work on it? Or would you totally abandon the process?
Amazing article for sure — this is something that I think those that aren’t using a defined deployment process would be able to follow this to the “T” very easily & quickly.
Jason Resnick
This is all great and I’m all for any process that makes it easy to rollback in case of a blow up. But my question is what would you do if you have a client that you work on their site from time to time, but they also work on it. The caveat here is that they don’t have any knowledge of source control and just make changes on the fly.
Would you “sync” their changes each time you work on it? Or would you totally abandon the process?
Amazing article for sure — this is something that I think those that aren’t using a defined deployment process would be able to follow this to the “T” very easily & quickly.