News for hackers. Stuff that matters.

A comment on Improving how we deploy GitHub. Parent comment

Re:Improving how we deploy GitHub by majormajor on Monday January 25, 2021 @09:15PM (#25911649)
> I would have expected the PR to be merged first before it gets served to the public, so even if you have to `git revert` and undeploy it, you still have a record of every version that was seen by actual users, even momentarily.

This sounds rather terrifying to me as well. Hopefully there's some sort of system for keeping around all those individual branches that made it out to prod, however briefly, for future debugging/auditing purposes if you ever need them.

It's never fun to have to be doing "what code was running at this time" investigations, but every once in a while it's the only way to really get to the root of something.

[ Parent | on HN ]
Re:Improving how we deploy GitHub by Existenceblinks on Tuesday January 26, 2021 @11:47AM (#25917984)
My ex-company has similar flow, but fix the terrifying part by (off-git-hosting, i.e. in-memory) merging ALL opened PRs to master and deploying straight to staging server. Any PR can be marked as excluded from a deploy. All PRs are ALWAYS based off master. tldr; master based pull requests as source of release.
[ Parent | on HN ]