RepoAnt
Screenshots Features View on GitHub Stars ...

Documentation

Everything needed to run, market, and publish RepoAnt.

This documentation covers installation, command reference, scenario simulation assets, and GitHub Pages deployment operations.

Setup and install

  1. Install with Homebrew: brew tap AasishDairelSahayaGrinspan/repoant && brew install repoant.
  2. Authenticate once: repoant login.
  3. Verify with: repoant list.

Command reference

  • repoant login: stores GitHub token with 0600 permissions.
  • repoant list: lists repositories available to your token.
  • repoant delete: interactive single repository delete.
  • repoant delete --multi: multi-select delete with DELETE count confirmation.
  • repoant protect add owner/repo: prevents accidental deletion.
  • repoant protect remove owner/repo: removes from protected list.

Scenario simulation pack

  • assets/scenario-login.svg: first-time login and token save.
  • assets/scenario-list.svg: repository inventory before cleanup.
  • assets/scenario-single-delete.svg: single-delete confirmation.
  • assets/repoant-screenshot.svg: multi-delete with typed confirmation.
  • assets/scenario-protected.svg: protected repositories excluded.
  • assets/scenario-token-missing.svg: missing token recovery guidance.

Media update workflow

  1. Record a real CLI flow for login, list, and delete cases.
  2. Export to GIF and replace assets/repoant-demo.gif.
  3. Keep screenshots at consistent aspect ratio for visual polish.
  4. Update captions in index.html if scenario wording changes.

GitHub Pages deployment

  1. Push to main branch.
  2. Workflow .github/workflows/pages.yml publishes website/.
  3. Public URL: https://aasishdairelsahayagrinspan.github.io/RepoAnt/.
  4. If first deploy, set Pages source to GitHub Actions in repository settings.

Troubleshooting

  • 404 on Pages: confirm URL casing uses /RepoAnt/ exactly.
  • Star count not loading: check GitHub API rate limits or network access.
  • No deployment: verify workflow permissions for pages and id-token.
  • Blank GIF area: ensure repoant-demo.gif exists in website/assets/.
Operational note: This documentation page is designed to support both users and maintainers so marketing content and deployment steps stay in sync.