Leaving Fwozen

Leaving is three steps, and the order matters. Do the middle one before the last one or you will leave a branch that cannot be merged to, with nothing left running to clear it.

The sequence

1. Lift the freezes, or let them expire. Uninstalling ends them anyway, but doing it first means the checks flip to passing while Fwozen is still there to write them.
2. In GitHub, remove fwozen from the required checks. Settings → Rules → Rulesets, open the rule named fwozen, and either delete it or set it to disabled. If your own rule required the check rather than Fwozen’s, edit that one and drop the fwozen context. This is the step to do first, and the reason is in the callout above.
3. Uninstall the GitHub App from your organisation’s Installed GitHub Apps page. Fwozen ends every active freeze, cancels every schedule, stops billing, and schedules your data for deletion 30 days later. No further writes to GitHub are possible after this, with or without your cooperation: the installation token is gone.

What is left afterwards

• Your rules stay yours. Everything Fwozen ever wrote is a GitHub object in your account, readable and editable by you, and the only one it creates is the ruleset that requires a check.
• Check runs stay on their commits. Historical fwozen results are part of GitHub’s record of those commits and are not ours to remove.
• Your Fwozen data is deleted after 30 days. Export the audit log before you go if you need it: GET /v1/audit/export streams CSV, and the dashboard’s audit page has the same button.
• Billing stops at the uninstall. There is no exit fee and no email required to cancel.

Reinstalling later is the ordinary install path. Nothing about a removed installation blocks it, and the enforcement step will find and reuse a correct ruleset it recognises rather than writing a second one.