Ashutosh00710 / Ashutosh00710/github-readme-activity-graph
CI (Node.js CI workflow) fails on every push/PR — "account is locked due to a billing issue"
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
The `Node.js CI` GitHub Actions workflow fails on every push to `main` and every pull request. The job never actually runs — it's blocked before checkout with the annotation: *"The job was not started because your account is locked due to a billing issue."* The `Greetings` workflow is affected the same way.
**To Reproduce**
1. Open a PR or push a commit to `main`.
2. Go to the **Actions** tab.
3. Open the `build (22.x)` job under `Node.js CI`.
4. See the annotation: "The job was not started because your account is locked due to a billing issue."
Example failing runs:
- [main push, 2026-05-17](https://github.com/Ashutosh00710/github-readme-activity-graph/actions/runs/25993803967)
- [PR #250, 2026-05-13](https://github.com/Ashutosh00710/github-readme-activity-graph/actions/runs/25809530853)
- [PR #252, 2026-07-29](https://github.com/Ashutosh00710/github-readme-activity-graph/actions/runs/30490986156)
**Expected behavior**
CI should run and report real pass/fail results on pushes and PRs, not fail immediately due to account billing status.
**Additional context**
This isn't a code bug — it's a GitHub Actions billing lock on the account/org running the workflows, so it can only be fixed by the repo owner (`@Ashutosh00710`) resolving billing on GitHub's side. Flagging it because it currently blocks all CI feedback on new PRs (including recent contributions like #252).
Contributor guide
Research direction
Open the Actions tab and inspect the Node.js CI and Greetings workflow runs, especially the build (22.x) job. Confirm that jobs stop before checkout with the billing-lock annotation; done means pushes to main and pull requests start running and report real results after the repository owner's GitHub billing issue is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 20/100