Switch modifications should never stop work.
Prod code push != prod infrastructure changes. Which is what the article is talking about. Specifically the agg. switching layer.
My reply is not about code deployments. It is about managing network devices with high visibility and impact.
I still stand by my original comment with a critical detail added:
Freeze prod ~infrastructure~ changes two weeks prior and two weeks after major holidays.
Push code all you want.
The RFO that they provided addresses link aggregation changes which are a part of an infrastructure change.
Also, they most likely scheduled this at this time due to the lower traffic, probably the lowest of the year for them. While half of Github was probably enjoying their families the other half was planning for this for a long time. Given the size of the operation I don't think anyone took it lightly.