News for hackers. Stuff that matters.
Re:Improving how we deploy GitHub by samc98 on Monday January 25, 2021 @05:58PM (#25910109)
How does this work if two (or more) engineers touch the same file at the same time?

EG: If two engineers have two different PRs open modifying `index.html`, how does that go to canary?

Re:Improving how we deploy GitHub by bswinnerton on Monday January 25, 2021 @07:23PM (#25910826)
Before every deploy your branch has master merged into it. There’s some clever work by Hubot while you’re in line to deploy to create a version of your branch that has the potential new master / main branch. If conflicts arise you fix them before it’s your turn to deploy.
Re:Improving how we deploy GitHub by rtpg on Tuesday January 26, 2021 @03:41AM (#25913726)
how deep does this deploy queue get? And does everything that lands on master have to first be deployed?

This seems like a bit tough for getting work done if you have enough people all waiting around for this

Re:Improving how we deploy GitHub by jules2689 on Tuesday January 26, 2021 @10:43AM (#25917068)
The deploy queue usually gets to be a couple of "trains" deep which usually includes work from 4-10 devs. This represents a couple of hours. We have had issues with it taking too long, but this work I wrote about has improved that! We continue to try to improve it.