Owner who disabled Copilot and workflows had ci turn red immediately

[PeterKellner]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Workflow Deployment

Discussion Details

My ci went turned red when I disabled copilot and all workflows. I I. learned I had to at least enable workflow or copilot to turn green again. When attempted to enable workflow or copilot, prevented and Owner/Adm must do it. I am Owner/Adm. My repo is being evaluated currently, appreciate any help.

[ankurmaurya01]

Hi @PeterKellner! 👋

This is a known edge case — when workflows are disabled at the repo level, any branch protection rules requiring CI checks to pass will immediately turn red (since no checks are running at all).

Here's what to try as Owner/Admin:

Step 1 — Re-enable workflows

1. Go to your repo → Settings → Actions → General
2. Under "Actions permissions", select Allow all actions and reusable workflows (or at minimum "Allow actions created by GitHub")
3. Click Save

Step 2 — If it says "Owner/Admin must enable" but you ARE the owner
This can happen if your repo is inside an Organization — org-level policies can override repo-level settings.

• Go to your Organization Settings → Actions → General
• Make sure Actions are not disabled at the org level
• Only org Owners can change this

Step 3 — Re-run your workflow manually
After re-enabling, go to Actions tab → select your workflow → click Run workflow to trigger a fresh run and turn CI green again.

Step 4 — Copilot is separate
Note: Disabling Copilot should NOT affect CI/CD — those are independent. Your CI went red purely because workflows were disabled, not because of Copilot.

If you're still blocked:

• Check Settings → Branches → look at branch protection rules and see which check is required
• Temporarily remove the required check, push a commit, then re-add it after CI is green

Hope your evaluation goes smoothly! 🙌

[Aj2280]

What you're seeing is usually caused by branch protection rules that require specific workflow checks to pass.

When Actions/workflows are disabled, those required checks can no longer run, so GitHub marks the branch status as failing or pending. Re-enabling workflows normally resolves this, but if GitHub is telling you that only an Owner/Admin can enable them—even though you're listed as one—there may be an organization-level policy or enterprise policy overriding the repository settings.

A few things to verify:

• Repository Settings → Actions → General: confirm Actions are enabled.
• If the repository belongs to an organization, check Organization Settings → Actions for restrictions that override repository settings.
• Review Settings → Branches and inspect any branch protection rules that require status checks.
• After Actions are re-enabled, rerun the affected workflow or push a new commit to regenerate the required checks.

If the repository is currently under evaluation or review by GitHub and the controls appear locked unexpectedly, it may also be worth opening a support ticket with GitHub Support and providing the repository URL and screenshots of the permissions message.

Can you confirm whether this repository is under a personal account or an organization, and what exact message you receive when attempting to re-enable Actions?