3 ms·
You actually never want an atomic commit for that class of changes across projects because HEAD should always be deployable to all services. It's obviously mess
by dehrmann 7y ago
You actually never want an atomic commit for that class of changes across projects because HEAD should always be deployable to all services. It's obviously messier at FAANG-scale, but with even 25 devs, not properly staging API-breaking changes leads to a lot of "only deploy commits before xxxx to service foo."