GitHub Actions is currently disabled for my account

[balaji-sangana]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Other

Discussion Details

GitHub Actions is currently disabled for my account.

Repository:
https://github.com/balaji-sangana/secverify

When I open the Actions page, GitHub displays:

"GitHub Actions is currently disabled for your account. Please reach out to GitHub Support for assistance."

I maintain this open-source security testing project and have added a GitHub Actions workflow:

.github/workflows/secverify-review.yml

The workflow is intended to run automated security code review and generate SARIF results for GitHub Code Scanning.

However, no workflow runs can start because GitHub Actions appears to be disabled at the account level.

I already attempted to contact GitHub Support, but the repository support form did not provide a GitHub Actions option.

Could someone please advise why Actions is disabled for my account and how I can have the restriction reviewed or re-enabled?

Thank you.

[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. ⭐

[TongyiDai]

That exact banner is different from a repository-level Actions policy. GitHub documents that when the message says “GitHub Actions is currently disabled for your account,” changing the repository settings will not restore access; the account is in a separate GitHub-controlled disabled state and GitHub Support must review it:

https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository

I would submit a ticket at https://support.github.com/contact while signed in as the owner of balaji-sangana. If the form does not offer an Actions category, choose the closest account/repository category and state in the first line that this is an account-level GitHub Actions disablement, not a workflow configuration problem. Include:

• the account and repository URL;
• the exact banner text and a screenshot;
• when it first appeared, with timezone;
• one workflow/run URL if GitHub created a run;
• confirmation that Settings → Actions → General allows Actions.

Do not include tokens, secrets, or the contents of private repository files. The community can help diagnose YAML and permissions, but it cannot remove an account-level restriction; only Support can do that.

[balaji-sangana]

Hello @TongyiDai ,

I am requesting a review of an apparent account-level GitHub Actions restriction.

GitHub account: balaji-sangana
Repository: balaji-sangana/secverify

I checked the repository's Actions configuration under:

Settings → Actions → General → Actions permissions

The repository is configured as:

“Allow all actions and reusable workflows.”

However, GitHub reports that GitHub Actions is disabled for my account and workflows cannot run.

This makes it appear that the issue is not caused by the repository-level Actions permissions.

The repository contains the workflow:

.github/workflows/secverify-review.yml

This workflow is intended for automated security code review and SARIF generation for GitHub Code Scanning.

I have attached screenshots showing the repository Actions configuration and the Actions behavior/message.

Could you please review the account-level restriction and let me know:

1. Why GitHub Actions is disabled for my account;
2. Whether the restriction is temporary or permanent;
3. Whether there is anything I need to change to comply with GitHub's policies; and
4. Whether GitHub Actions can be re-enabled for my account.

Thank you for your assistance.

[TongyiDai]

Hi @balaji-sangana — just to clarify, I’m a GitHub community member, not GitHub staff, so I can’t review or remove account-level restrictions.

The text you prepared is suitable for a support ticket, but it needs to be submitted through the signed-in GitHub Support portal:

https://support.github.com/contact

Please include the exact banner, the repository URL, screenshots, and the approximate time the restriction first appeared. Avoid posting billing details, tokens, or other private account information in this public discussion.

Once submitted, only GitHub Support can explain the restriction or re-enable Actions. If useful, you can update this discussion with the outcome after Support responds.

[omkar8425]

Thanks for the detailed report. This looks like an account-level GitHub Actions restriction, rather than an issue with the workflow file itself.

GitHub's documentation specifically notes that when the message “GitHub Actions is currently disabled for your account” appears, changing the repository's Actions settings will not restore access because the account may be in a separate GitHub-controlled disabled state. In that situation, GitHub Support needs to review the restriction.

Since you have already contacted Support and could not find an Actions-specific category, I would recommend submitting the request through the general GitHub Support portal and clearly mentioning:

• Username: balaji-sangana
• Repository: balaji-sangana/secverify
• GitHub Actions is disabled at the account level
• The repository contains a legitimate security-testing workflow
• The workflow is intended to perform automated security review and produce SARIF results for Code Scanning
• The Actions page displays the account-level disabled message

GitHub's documentation confirms that Support can assist with GitHub Actions issues.

I would also avoid repeatedly changing repository Actions settings, because an account-level restriction cannot be resolved from the repository settings. The most appropriate next step is for GitHub Support to review why the account was restricted and determine whether Actions can be re-enabled.

Hopefully Support can clarify the reason for the restriction and restore Actions if the repository and workflow comply with GitHub's policies.

[balaji-sangana]

Hello @omkar8425 ,

Thank you for confirming that this appears to be an account-level GitHub Actions restriction.

I have verified that the repository-level Actions setting is already configured to “Allow all actions and reusable workflows.”

Could you please proceed with reviewing the restriction on my account balaji-sangana and let me know:

What caused GitHub Actions to be disabled on my account?
Is the restriction temporary or permanent?
Is there any policy or configuration issue that I need to address?
Can GitHub Actions be re-enabled for my account?

The affected repository is:
balaji-sangana/secverify

The workflow is used for automated security code review and SARIF generation for Code Scanning.

I can provide any additional information or verification required.

Thank you.

[jay1466]

I’m also experiencing the same issue where GitHub Actions is disabled at the account level, even though my repository’s Actions settings are configured correctly.

I have already checked the repository settings, but the message “GitHub Actions is currently disabled for your account” still appears.

Has anyone received a response from GitHub Support or found a way to get the account-level restriction reviewed and Actions re-enabled?

Any guidance would be appreciated. Thank you!

[amiriguesss]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Other

Discussion Details

GitHub Actions is currently disabled for my account.

Repository: https://github.com/balaji-sangana/secverify

When I open the Actions page, GitHub displays:

"GitHub Actions is currently disabled for your account. Please reach out to GitHub Support for assistance."

I maintain this open-source security testing project and have added a GitHub Actions workflow:

.github/workflows/secverify-review.yml

The workflow is intended to run automated security code review and generate SARIF results for GitHub Code Scanning.

However, no workflow runs can start because GitHub Actions appears to be disabled at the account level.

I already attempted to contact GitHub Support, but the repository support form did not provide a GitHub Actions option.

Could someone please advise why Actions is disabled for my account and how I can have the restriction reviewed or re-enabled?

Thank you.

That's an account-level restriction, not something the workflow file can trigger or fix — GitHub turns Actions off for a whole account when Trust & Safety flags it, or when there's a billing/policy block behind the scenes. A few things are worth checking, and the repo support form won't help because the restriction isn't on the repo, it's on you.
Things that commonly cause this:

• Account flagged by Trust & Safety. Usually an automated abuse/spam flag, or something that got picked up as "automation-heavy" or ToS-adjacent. New-ish accounts and accounts that mass-fork/PR tend to get hit.
• Billing problem. Failed payment, expired card, or a payment method that got flagged. Check https://github.com/settings/billing — if there's a red banner about payment or a "your account is restricted" notice, that's your answer.
• Sanctions / region restriction. GitHub disables Actions (and Pages) for accounts in sanctioned regions. If you're connecting from one, this is a known block and only support can clarify.
• Organization or enterprise policy. If the repo is under an org, an owner may have disabled Actions at the org level. Account-level wording makes this less likely, but worth ruling out.
• A suspension or "spam" flag you may have missed. Check the email on the account, including spam — GitHub usually sends a notice. Look for anything from GitHub Support or Trust & Safety about a suspended/flagged account.
  The part people usually get wrong: use the account appeal path, not the repository form. Go to https://support.github.com/contact → choose "Account and Profile" (or "Appeal a decision" / "My account is suspended or flagged"). If you have an email from Trust & Safety, reply directly to that email — it lands in the queue far faster than a fresh ticket. In the ticket, state plainly that Actions is disabled account-wide with the exact banner text, link the repo, and ask what the restriction is and how to get it reviewed. Avoid opening multiple tickets; duplicates tend to slow it down.
  While you wait, also double-check https://github.com/settings/actions and the repo's Settings → Actions → "Allow all actions and reusable workflows" — if a toggle looks greyed out or missing, that confirms the account-level block.
  One honest caveat: nobody here can flip that switch for you. Only Trust & Safety can review and re-enable it, and appeals can take a few days. If the first ticket gets a canned reply, reopen it or reply with "requesting human review of the account-level Actions restriction" — that wording tends to get it escalated instead of auto-closed.