Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

P0 infra: GitHub Actions frozen above the repo — zero runs on all 30 open PRs (org-level switch or billing; not a workflow regression)

Aperta
  • Qualcosa non va?
#790 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
3/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github, github-actions
Ambito
devops

Direzione di ricerca

This is an org-console outage, not a code change: no commit in the repository can fix it. The payload points to https://github.com/organizations/OpenTollGate/settings/actions and the billing page as the places an owner must check. A newcomer should not start here; the only useful step is to confirm the outage is still present on a new push.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Diagnosed from the #665 CI-sweep follow-up (zero check runs on all 30 open PRs). TL;DR: the workflows are innocent — the event→run pipeline is frozen at the ORG level. No commit to this repository can fix it; it needs one org-console action by an owner.

@felixfelix-bot — flagging for the owner lane: this blocks the entire approval queue's CI backing (PR-REVIEW.md's CI-rollup step has nothing to roll up).

Evidence (all first-party, this session)

Probe Result
PRs #775/#779 (+ sample of the 30 open) 0 check runs
Fresh trivial PR from a fresh branch (#789, the commissioned probe; head 04d8887) 0 suites, 0 runs at +75 s and +135 s
Push to main (tip 4614ac2, pushed 2026-10-08) 3 github-actions suites in queued, no runs behind them
Org-level dynamic workflows (Dependabot / Dependency Graph) runs created, queued, never start — since at least 2026-10-05
Last real pull_request/push runs of any workflow 2026-08-27

What it is NOT (each checked)

  • Not the on: pull_request configs. All five workflows on main carry correct triggers (test.yml's branches: [main, master, develop] matches every open PR; gitleaks has bare pull_request:; build-package has pull_request: with only a paths-ignore: **.md that cannot suppress gitleaks or test.yml). A path-filter break also cannot explain zero runs on PUSH events, nor Dependabot queueing forever.
  • Not the four suspected change-sets. #759 (+5/−1 gitleaks config), #740 (no workflow-file changes), #710/#713 (build-package job edits + a 3-line test.yml addition) — none touch event gating, and main's current on: blocks post-date all of them and are intact.
  • Not repo settings. /actions/permissions → enabled: true, allowed_actions: all; all workflows state: active; default branch main carries the workflows; runs-on: ubuntu-latest everywhere (public repo, free hosted runners — no self-hosted fleet to go dark); no concurrency: zombies (zero in_progress runs exist; only build-package/router-test even declare groups).

What it IS

Runs are neither created (PR/push workflows: suites bookkeep, runs never spawn) nor started (dynamic: created, queued for days). With every repo-level control verified green, the remaining causes are above the repo — in order of likelihood:

  1. Org-level Actions policy is Off/Restrictive — https://github.com/organizations/OpenTollGate/settings/actions. The repo's enabled: true is overridden by the org switch. Timeline fits: Actions was deliberately disabled for the ngit migration (documented in .ngit/README.md, runs stop 2026-08-27); the fork consolidation (#758) re-homed the org ~2026-10-05; the REPO switch came back on — the ORG switch (or the org's billing state) did not. The org API is admin-gated (403 from the diagnostic account), so this could not be read programmatically.
  2. Org billing hold / suspension on the free plan — same signature (runs accepted, nothing executes); check https://github.com/organizations/OpenTollGate/settings/billing.

The fix (owner console actions, ~2 minutes)

  1. Org Settings → Actions → General: set Actions permissions: Allow (and "All actions and reusable workflows" or the previous policy), or explicitly enable for this repository.
  2. Check Billing & Plans for a hold.
  3. Cancel the stale queued Dependabot runs (some are 4+ days old), then push any commit or re-run a workflow — the probe steps in this issue reproduce in seconds if it is still broken.
  4. Confirm on the tracker: any open PR should immediately grow its check suite.

Probe artifacts

Probe PR #789 (closed; branch deleted) — the full transcript is in its close comment. No in-repo changes were made or are needed; when Actions returns, every open PR will get checks on its next push (or via re-run from the PR page for unchanged heads).

Lingua principale
Go
Stelle
12
Fork
14
Merge medio
1g 5h
PR unite (30g)
232

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di OpenTollGate/tollgate-module-basic-go

Tutte le issue di OpenTollGate/tollgate-module-basic-go

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.