311–320 of 425 posts
You can literally watch GitHub explode bit by bit. Take a look at the GitHub Status History; it's hilarious: https://www.githubstatus.com/history .
Someone should make a timeline chart from that, lol.
Earlier quoted context omitted.
> Basically their SOC2 (or whatever) says they have to use GitHub Our SOC2 doesn't specify GitHub by name, but it does require we maintain a record of each PR having been reviewed. I guess in extremis we could email each other patch diffs, and CC the guy responsible for the audit process with the approval...
Does SOC2 itself require that or just yours? I'm not too familiar with SOC2 but I know ISO 27001 quite well, and there's no PR specific "requirements" to speak of. But it is something that could be included in your secure development policy.
Earlier quoted context omitted.
Probably Worth taking an honest look at whether your CI could just be an SQS queue and a Mac mini running under your desk though
For my OSS work that is about $699 over my budget
Earlier quoted context omitted.
Someone should make a timeline chart from that, lol.
Here it is. It looks like they are down to a single 9 at this point across all services: https://mrshu.github.io/github-statuses/
Earlier quoted context omitted.
Does SOC2 itself require that or just yours? I'm not too familiar with SOC2 but I know ISO 27001 quite well, and there's no PR specific "requirements" to speak of. But it is something that could be included in your secure development policy.
Yeah, it’s what you write in the policy.
If you'd have asked me a few years ago if anything could be an existential threat to github's dominance in the tech community I'd have quickly said no. If they don't get their ops house in order, this will go down as an all-time own goal in our industry.
Github lost at least one 9, if not two, since last year's "existential" migration to Azure.
Something this week about "oops we need a quality czar": https://news.ycombinator.com/item?id=46903802
GitHub no longer publishes aggregate numbers so here they are parsed out. It looks like they are down to a single 9 at this point across all services: https://mrshu.github.io/github-statuses/
Earlier quoted context omitted.
Lots of teams embraced actions to run their CI/CD, and GitHub reviews as part of their merge process. And copilot. Basically their SOC2 (or whatever) says they have to use GitHub. I’m guessing they’re regretting it.
> Basically their SOC2 (or whatever) says they have to use GitHub Our SOC2 doesn't specify GitHub by name, but it does require we maintain a record of each PR having been reviewed. I guess in extremis we could email each other patch diffs, and CC the guy responsible for the audit process with the approval...
I have cleaned up more than enough of them.