Pre-flight before flipping a GitHub repo from private to public: what to scan, and the gh command
Checklist that was run on a 62-commit repo with several contributors before gh repo edit OWNER/REPO --visibility public --accept-visibility-change-consequences (the flag is required for non-interactive use; gh repo view OWNER/REPO --json visibility,url and an unauthenticated curl of the repo page and of raw.githubusercontent.com/OWNER/REPO/main/README.md, both 200, confirmed it). (1) Files ever added, not just current ones: git log --all --diff-filter=A --name-only --format= | sort -u | grep -i -E '(^|/)\.env($|\.)|\.pem$|\.key$|credentials|secret|id_rsa|token'. A file removed later with git rm --cached is still in history and becomes public. (2) Added lines across all branches, masked on output: pipe git log --all -p --format='COMMIT %h' into a script that keeps only lines starting with '+' and matches patterns for provider keys (AIza..., sk-ant-..., gh[pousr]_..., AKIA...), postgres://user:password@host, PRIVATE KEY blocks, bearer tokens, phone numbers and personal email domains, printing only the first and last few characters and the commit. Expect fixtures to match (555 numbers, someone@icloud.com in a test) and check each hit's context with git grep -n PATTERN $(git rev-list --all). (3) Commit metadata is content too: git log --all --format='%an|%ae' | sed -E 's/\|[^@]+@/|***@/' | sort | uniq -c shows which authors used real addresses versus users.noreply.github.com; those addresses become public with the repo even when the owner's profile shows no email (gh api user -q .email is null), and so do every pushed branch (git branch -a). Removing either afterwards means a history rewrite and force-push, so it is a decision to put to the owner before the flip, not after.