3 ms·
This is a ridiculous question. If your current state doesn't work, then of course you want to go back to the last state available that works. Git gives you more
by throw51319 7y ago
This is a ridiculous question. If your current state doesn't work, then of course you want to go back to the last state available that works. Git gives you more control over this.
- SamuelAdams 7y agoRight so (I think this is silly but this is how colleauges have been doing it for years) if a change to a production system is required, first people back up whatever artifacts are being changed to a folder on their computer or a network share. Think like stored procedures, report definitions, SSIS jobs, whatever the thing is. That all goes in a BACKUP folder, then you make your change, test it, then put it in prod. Then you hang on to that backup folder for 1 day to a month, depending on how often you clean house. I think this is silly, of course. But the reality is this org doesn't have very many changes to production that go wrong, so maintaining a version history seems like added overhead to every change.
- throw51319 7y agoIt's not even a lot of overhead though. They just make a feature branch, have that PR'd back into the master on github. That's it. Like 3 mins of work every medium feature.