That actually seemed reasonable when I hit it, because you can easily accidentally have an action triggered on commit that makes a new commit, ending up in an infinite loop.
The workaround is to use a token tied to you instead of GitHub Actions, so you get charged (or run out of quota).
> The workaround is to use a token tied to you instead of GitHub Actions, so you get charged (or run out of quota).
You get charged no matter what, a personal access token doesn’t change anything.
If they are concerned about infinite loops then put a limit on how many workflows can be triggered but another workflow. Each time a workflow chains off another pass along some meta data of “runsDeep” and stop when that hits X, which can be configured.
No, requiring a PAT to kick off a workflow from a workflow is gross and makes zero sense. I don’t want every tag associated with my user, I want it to be generic, the repo itself should be attributed. The only way to solve this is to create (and pay for) another GH user that you create PAT tokens under. A bunch of overhead, cost, and complexity for no good reason.
The workaround is to use a token tied to you instead of GitHub Actions, so you get charged (or run out of quota).