github-release

# GitHub Release Sanitize and release projects to GitHub. Two-phase workflow: safety checks first, then tag and publish. ## Prerequisites - `gh` CLI installed and authenticated (`gh auth status`) - `gitleaks` installed for secrets scanning (`brew install gitleaks` or download from GitHub) - Git repository with a remote configured ## Workflow ### Phase 1: Sanitize Run these checks before any public release. Stop on blockers. #### 1. Scan for Secrets (BLOCKER) ```bash gitleaks detect --no-git --source=. --verbose ``` If secrets found: **STOP**. Remove secrets, move to environment variables. Check git history with `git log -S "secret_value"` — if in history, use BFG Repo-Cleaner. If gitleaks not installed, do manual checks: ```bash # Check for .env files find . -name ".env*" -not -path "*/node_modules/*" # Check config files for hardcoded secrets grep -ri "api_key\|token\|secret\|password" wrangler.toml wrangler.jsonc .dev.vars 2>/dev/null ``` #### 2. Remove Personal Artifacts Check for and remove session/planning files that shouldn't be published: - `SESSION.md` — session state - `planning/`, `screenshots/` — working directories - `test-*.ts`, `test-*.js` — local test files Either delete them or add to `.gitignore`. #### 3. Validate LICENSE ```bash ls LICENSE LICENSE.md LICENSE.txt 2>/dev/null ``` If missing: create one. Check the repo visibility (`gh repo view --json visibility -q '.visibility'`). Use MIT for public repos. For private repos, consider a propr...