Hello we want to cancel our Enterprise Trial,

[Jacquiwolrad]

🏷️ Discussion Type

Question

Body

What are the repercussion if we do, we can't lose any repos but we need more minutes than the free trial offers.

[Eslammohammedd]

1. No Repository Loss

You will not lose any repositories. Your code, history, issues, and pull requests remain exactly where they are. Upgrading simply unlocks higher resource limits and advanced collaboration features on those existing repos.
2. Actions Minutes Repercussions

The primary change is how your CI/CD pipelines are handled:

Increased Allotment:

    GitHub Pro (Personal): Increases from 2,000 to 3,000 minutes/month.  

    GitHub Team (Org): Increases from 2,000 to 3,000 minutes/month.  

No More "Hard Stops": On the Free plan, workflows simply fail once you hit the limit. On a paid plan, you can set a Spending Limit (e.g., $5 or $10). This allows your jobs to keep running by charging a per-minute fee (currently $0.006 for Ubuntu) only after you exhaust your 3,000 free minutes.  

Self-Hosted Change: Note that as of March 2026, even self-hosted runners in private repositories now consume from your minute quota or incur a small platform fee ($0.002/min) once the quota is hit.  

3. Immediate Benefits (Private Repos)

Beyond minutes, upgrading converts your private repositories into "Pro" repositories, giving you:

Branch Protection: Prevent anyone (including yourself) from pushing directly to main without a passed test or a code review.

Code Owners: Automatically assign reviewers based on which part of the code was changed.  

GitHub Pages: The ability to host private documentation or internal sites directly from a private repo.

4. Important 2026 Billing Update

Be aware that starting June 1, 2026, GitHub is unifying Copilot and Actions billing into a system called GitHub AI Credits.

Your monthly subscription will include a set amount of credits.

Copilot Code Reviews will now consume both AI Credits and Actions minutes simultaneously.

[Jacquiwolrad]

I want to downgrade back to my previous package not upgrade, is that possible with no loss or service? When i go to cancel it say orgnaizations are at risk?

[Eslammohammedd]

Query successful

The "at risk" message is definitely one of the more stressful warnings GitHub shows, but in reality, it's more about security and workflow features than it is about your data itself.

If you decide to downgrade your organization back to the Free tier, here is exactly what "at risk" means for you:

1. Your Code is 100% Safe

First, the relief: You will not lose any repositories. All your code, history, issues, and pull requests remain exactly where they are. GitHub does not delete or lock your private repositories when you downgrade; it just changes the "tools" available to manage them.
2. Why GitHub says you are "at risk"

When you move to a Free plan, you lose Advanced Collaboration Tools on private repositories. GitHub considers your organization "at risk" because:

Branch Protection Rules will turn off: If you have rules that prevent pushing directly to main or require a passing test before merging, these will be disabled for private repos. This means anyone with write access could accidentally overwrite your main branch.

Required Reviewers: You can no longer force a second pair of eyes on code changes in private repos.  

GitHub Pages (Private): If you are hosting a private documentation site from a private repo, it will be taken offline (only public repos can host Pages on the Free plan).

3. The "Actions Minutes" Repercussion

Since you mentioned needing more minutes, this is the part that will affect your service most:

The Hard Cap: On the Free plan, you drop from 3,000 minutes back to 2,000 minutes per month.

No Overages: On a paid plan, you can set a "Spending Limit" to keep running builds once you hit your limit (charging a small fee per minute). On the Free plan, your workflows will simply stop working until the next month once you hit 2,000 minutes.

4. 2026 Specifics to Watch

   Self-Hosted Runners: Remember that as of March 2026, even using your own servers (self-hosted) for private repos now consumes your minute quota or incurs a platform fee.

   AI Credits: If your team uses Copilot, keep in mind the June 1, 2026, transition to GitHub AI Credits. Downgrading now will prevent your organization from being part of that unified billing system.

[ardaltunel]

As far as I know, deleting the Copilot subscription or running out of included minutes should not affect your repositories at all.
Your repos, commits, issues, PRs, and code remain untouched since Copilot is only an additional AI service layer.

The main repercussion would simply be losing access to Copilot features or hitting usage limits until the next billing cycle or upgrade.
Still, it’s probably best to double-check GitHub’s official billing documentation before making any changes.

[moriletech000]

If you’re talking about upgrading from the free plan just to get more CI/CD minutes or usage time, then usually there aren’t really any major “repercussions” in terms of losing repositories. Your repos normally stay intact.

The main difference is mostly billing and usage limits. Once the free trial ends, you’d just start paying based on the plan or the extra minutes you use.

I’d still recommend double-checking:

• whether private repos stay private on your chosen plan
• what happens if payment fails
• whether usage automatically renews
• if there are storage or bandwidth limits too

But in general, upgrading for more minutes shouldn’t delete or affect your repositories. The repos are usually separate from the compute/minutes quota.
So how about trying that and see what happens... Anyways good luck with it I'll be here if you still have any issues to fix

[Jacquiwolrad]

i want to down grade not upgrade, eg leave enterprise for a lower teir.

[moriletech000]

If you’re downgrading from Enterprise to a lower tier, you normally should not lose your repositories. In most cases, the repos stay exactly where they are — you just lose access to some Enterprise-only features, higher limits, or extra build/runtime minutes.

Still, before downgrading, I’d honestly recommend doing a few things just to be safe:

• make sure all important repos are fully pushed/synced
• create local backups or mirrors of critical repos
• check whether the lower tier has limits on private repos, storage, or team members
• verify which features will stop working after the downgrade

Usually the actual downgrade process is pretty straightforward:

1. Go to Billing or Subscription settings
2. Choose “Change Plan” or “Downgrade”
3. Review what features/resources you’ll lose
4. Confirm the downgrade

The biggest thing to watch for is usually CI/CD minutes, storage quotas, or advanced collaboration features — not the repos themselves.

So honestly, I wouldn’t expect your repositories to suddenly disappear, but backing everything up first is still the smart move before changing tiers.