If we hard reject actions, we’ll probably end up with the prior status quo: Jenkins.
We'd love to look into your specific case if you want shoot me an email: [email protected]
Either way, we're looking into this issue and I'll post an update here once we've learned more.
Quietly editing your comment after being called out to hide it is even worse.
Microsoft notoriously hires a lot of people from the Federal Sector who unfortunately appear to be mostly right-wing religious zealots.
https://github.com/thejoebourneidentity/vm-stats
I know multiple people who left GitHub after it was acquired by Microsoft because of unsatisfying experiences they previously had with Microsofties. It seems that they made the right call.
Still, what could possibly make anyone think posting a personal twitter handle for this was a good idea. That alone makes me question that he should have the role he does at GitHub.
Everyone here lives under capitalism. Making money is fine. Saying "If you pay us, we'll take your money" is totally expected. But that's not what they're doing here.
But GitHub is now a MAGA-converged organization pushing a social agenda, and you can see it in the quality of their engineering.
AFAIK, there has been no communication/acknowledgement of this as an issue. It makes it hard to decide to pick GHCR as a registry of choice.
Simple fix was to add `logout: false` to the action options.
And yet it is still half baked. We prepared for this with internally shared docs and the branch built in private for a while, but still had to roll back yesterday because the scheduler reverted to putting jobs wherever it pleased (including on ephemeral runners that already have a job) and randomly cancels large sets of jobs too.
I have been of the opinion that investing into GH Actions at this stage is purely sunken cost (at my org), and I'm not moving until the team behind this thing ships something that doesn't break half the time. These have been seriously frustrating months, because no amount of working around this messy code[1] made of 5 layers of MS style .NET (seriously, deleting a directory goes 5 layers deep in the call stack) will ever produce a stable product. They don't even know their own code base that well, when they first attempted ephemeral runners with `--once` it turned out the thing they produced could never work (because the server-side scheduler loves pipelining jobs to machines and failing miserably when these disappear, job times out after 20 minute of waiting type)
[1]: https://github.com/actions/runner