Re:A Git catastrophe cleaned up
by ams6110 on Wednesday December 21, 2016 @08:17PM
(#13234038)
The edge case could be mitigated by having a pre-defined development workflow and not seat-of-the-pants cowboy commits of "backend" and "frontend" changes that were in reality interwoven. Or even a basic code review where someone hopefully would say "WTF are you doing!?"
[ Parent
| on HN ]
Re:A Git catastrophe cleaned up
by SOLAR_FIELDS on Wednesday December 21, 2016 @08:23PM
(#13234051)
Agree - this should have been a single push and dev should have squashed commits together where it makes sense to. I get in the dev stage you might be all over the place but a well-designed codebase with separation of concerns should have allowed the dev to group like commits into single areas and brought it down to something more manageable like 20 commits instead of 400.