FAQ

FAQ

Does this only work for one GitHub account?

No. The tool can use whichever authenticated account is active for the selected host, and it can switch accounts when needed.

Where did the GitHub auth controls go in the GUI?

They now live on the dedicated Settings page. Quick Refresh, Login, Logout, and Settings actions also stay available in the lower status bar.

Does this only work for one repository?

No. The GUI can load many repositories, let you check one, many, or all, and then run cleanup sequentially.

Does the app warn me before cleanup?

Yes. The app shows an every-launch warning and Terms of Service acceptance screen, and the dashboard still requires the destructive cleanup safety arm switch before execution.

What should I run first?

Start with:

gh-actions-cleanup --repo OWNER/REPO --all --dry-run --yes

Is this reversible?

Not generally. Workflow runs, artifacts, caches, and workflow configuration changes should be treated as destructive.

Does the tool store my GitHub token?

No. It relies on GitHub CLI authentication and stores only the last host, account, and repo for convenience.

Does the app protect against accidental token display in logs?

Yes. The native app now redacts common token and key patterns before writing streamed output into the GUI log panel.

Does the app include built-in help files?

Yes. The native app bundles help, security notes, terms, project info, and brand documentation directly inside the app package.