1: https://gitlab.com/gitlab-org/gitlab/-/issues/402616 2: https://github.com/microsoft/vcpkg/issues/30481
"Software Engineer John was tasked to add a new logo to the website, when he was done he submitted a pull request of his feature branch into his organization's github repository for the website so that his team members could approve the changes before automation (like Github Actions) deployed live as a new version of the website."
It is also apparent that GitHub Actions has chronically been struggling to operate normally for at least once a month for years.
There is no question that GitHub has been more unreliable than if you were to use a self-hosted GitLab or Gittea instance yourself as I said before [1].
https://blog.gitea.io/2023/03/gitea-1.19.0-is-released/#-git...
it's certainly a risk you'll need to evaluate when planning your desired build process.
https://www.githubstatus.com/history
github has had 55 outages in 3 months. thats nearly an outage every two days.
the last six months of 2022 had 74 outages. In many shops thats tangibly worse than what their local greybeard Linux admin maintains.
arguments against spinning up my own gitlab/gitea/jenkins/whatever in podman under systemd are starting to ring pretty hollow lately.
I mean Github Actions was released 5 years ago[0]. I imagine the infrastructure for actions is more susceptible to outages than the fairly simple features Github offered previously. It makes sense that the number of outages would increase with the additional complexity in the infrastructure.
[0]: https://resources.github.com/devops/tools/automation/actions...
Besides, Microsoft surely has 24/7 watch of their infrastructure, even on weekends, it's a huge company.
[touches nose]
I'm just jumping up and down how awful this representation is. iso8601 (YYYY-MM-DD) is a settled debate at this point.
