gm3dmo/the-power/cleanup-test-data

Cleanup Test Data

Remove resources created by the-power scripts.

Working directory

All cleanup scripts must be run from the root of a the-power clone.

Find an existing clone:

find ~ -maxdepth 5 -name "delete-repo.sh" -path "*/the-power/*" 2>/dev/null

Safety warnings

• Deletions are IRREVERSIBLE. There is no undo.
• Always verify .gh-api-examples.conf points at the correct server.
• Review the target org and repo values before deleting.
• GHES-only operations (suspend/unsuspend) will not work on github.com.

Quick cleanup: delete the org

The fastest way to clean up everything is to delete the entire org:

curl -X DELETE \
  -H "Authorization: token ${GITHUB_TOKEN}" \
  "${GITHUB_API_BASE_URL}/orgs/${org}"

This removes the org and all its repos, teams, and other resources.

Cleanup by category

Repositories

Teams

Branch protection and rulesets

Webhooks

Environments

Secrets and keys

Other

GHES-only: suspend and unsuspend users

Examples

./delete-repo.sh my-test-repo              # delete a specific repo
./delete-team.sh alpha                      # delete a team
./delete-environment.sh staging my-repo     # delete an environment
./suspend-a-user.sh testuser               # suspend a GHES user

Error handling

• 404 — resource does not exist or was already deleted.
• 403 — token lacks delete_repo or admin:org scope.
• 422 — resource has dependencies that prevent deletion.

Boundaries

• Always confirm with the user before running any delete script.
• Verify the target instance — check hostname and org values.
• Do not delete resources you did not create on shared instances.
• Do not display the GITHUB_TOKEN. Show only the first 8 characters.