GitHub Actions silently disabled on public fork - permissions API says enabled, all triggers 422, support ticket #4890228 auto-closed to self-service

[satwareAG-ironMike]

Situation

satwareAG/spec-kit (public fork of github/spec-kit, used for spec-driven development tooling by a German software company) has had zero GitHub Actions activity since 2026-10-14T12:01Z. No notification was received.

Evidence (all probes 2026-10-20..22, logs available)

Probe	Result
Scheduled / push / pull_request triggers	zero runs for 8+ days; 6 daily scheduled runs missing
POST .../workflows/{id}/dispatches	HTTP 422 "Actions has been disabled for this repository"
GET /repos/satwareAG/spec-kit/actions/permissions	{"enabled":true,"allowed_actions":"all"}
PUT .../actions/permissions (enabled=true)	204 success, does not restore execution
All workflows	state: active
Repo flags	not archived, public, not suspended
Sibling org repo (doctrine-firebird-driver)	Actions ran normally through the same window
githubstatus.com	all systems operational throughout

This matches the "GitHub-controlled disabled state" your docs describe ("...changing these settings won't restore access. Contact GitHub Support for review.").

Support history

Support ticket #4890228 ("GitHub-controlled Actions disable on satwareAG/spec-kit - review and reinstate", category Repositories) was auto-closed by the virtual assistant with a pointer to self-service resources. We understand plan-tier limits on support; posting here per that instruction, asking staff to escalate the underlying restriction for review.

What our workflows are

Lint/test/privacy only (ruff, pytest, bats, shellcheck, markdownlint, CodeQL), SHA-pinned first-party actions, no self-hosted runners, no high-volume or crypto usage. If an abuse-control signal fired, it is a false positive - we will remove any workflow GitHub identifies as the trigger.

Impact / ask

Branch protection with 6 required checks now blocks every merge of upstream syncs; we run full local CI matrices as an interim control, which is not sustainable. Ask: confirm the disable scope (repo/org/account), and review for reinstatement.

---

AI-generated disclosure: this post was authored by an AI agent (Jane Alesi, OpenCode, model: Qwen 3.8 Flash Next) on behalf of the account holder.

[github-actions[bot]]

Thank you for your interest in contributing to our community! We currently only accept discussions created through the GitHub UI using our provided discussion templates. Please re-submit your discussion by navigating to the appropriate category and using the template provided.

This discussion has been closed because it was not submitted through the expected format. If you believe this was a mistake, please reach out to the maintainers.