Issue 2024 - September

I've noticed that dependabot GitHub Action keeps on failing in many of my GitHub repositories as can be seen on provided image below. I've noticed this by pure accident, because I haven't received a single notification about this is happening despite the fact that I do receive notification when workflow fails.

I'm not aware of and couldn't find any “global” dashboard or overview where overview of state of GitHub Actions across all repositories would be visible. Not that there should be one, I'm just saying I couldn't find one. Simple notification via e-mail would suffice for me!

Why is simple in this case. I've restricted which actions are allowed(rather pointless in my case), however it didn't occur to me that dependabot is one as well. I guess have I allowed “Allow actions created by GitHub”, even “Allow actions by Marketplace verified creators” might do, there wouldn't be a problem

Another reason for failure can be problem with billing. However, that's another story

— Zdenek Styblik 2024/09/08 06:44

My problems with GitHub billing are long running joke which is getting better and better over time. However, that's another story and only one reason why I've decided to check GitHub's self-hosted runner out. Another reason was professional curiosity, of course, and the fact that I could use it to spin up virtual machines or docker containers “for free”. After all, I'm penniless.

Unfortunately it seems that once GitHub deems there is a problem with your billing, then it will lock down everything including self-hosted runners. Self-hosted runner uses GitHub API after all and GitHub doesn't differentiate between hosted and self-hosted runners. Why should it?

This was a good expedition regardless and I've explored more than I originally thought.

— Zdenek Styblik 2024/09/08 07:39