GitHub Actions silently disabled on public fork since 2026-10-14 - permissions API says enabled, all triggers 422 (ticket #4890228 closed to self-service)

[satwareAG-ironMike]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Other

Discussion Details

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Other

Discussion Details

GitHub Actions has produced zero runs on our public fork satwareAG/spec-kit since 2026-10-14T12:01Z. No notification was received. Support ticket #4890228 was auto-closed to self-service resources, so we submit the case here per that instruction.

(Note: resubmission of https://github.com/orgs/community/discussions/210949, which the format bot closed because it was posted via API without this template.)

Evidence (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" the docs describe ("...changing these settings won't restore access. Contact GitHub Support for review.").

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: branch protection with 6 required checks 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.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐