ghit

Ghit

Command-line toolkit for GitHub: authenticate once, set a repo, and work with issues in bulk or interactively. Includes a generator that syncs the CLI surface with the GitHub OpenAPI spec.

Install

pnpm add -g ghit
# or npm i -g ghit

Quick start

• Login: ghit login (opens browser flow, stores token locally)
• Set default repo: ghit set-repo owner/name
• Optional: enable Use Current Repo for Commands in ghit config to auto-detect repo from your current git workspace
• Inspect info: ghit info
• Work with issues (interactive): ghit issues to list, view, close/reopen, edit, or delete
• Seed/update/delete issues in bulk: ghit issues:seed, ghit issues:update, ghit issues:delete

Auth and repo resolution

• When Use Current Repo for Commands is enabled, Ghit resolves the active repository from remote.origin.url in your current workspace.
• If Git credentials are already available for that repo (via your git credential helper), Ghit reuses that token for API calls.
• If no workspace credential is available, Ghit falls back to the token saved by ghit login.
• If workspace detection is disabled or no git repo is found, Ghit uses the configured default_repo.

Generated API commands (dynamic)

The CLI can generate commands directly from the GitHub OpenAPI spec. This keeps available commands and params in sync with GitHub without hand-coding.

• Generate commands (writes .ghit/apis.generated.js):

  ghit generate:apis
  

• Use generated commands (examples):
  • Create issue: ghit issues:create --title "Bug" --owner org --repo repo
  • List issues: ghit issues:list-for-repo --owner org --repo repo
  • Get single issue: ghit issues:get --owner org --repo repo --issue_number 123

Notes

• The generator runs once and the CLI will auto-load .ghit/apis.generated.js on subsequent runs.
• Only the command usage matters; you do not need to edit the generated file by hand.

Contributing

Contributing

Contributions are welcome! Please follow these steps:

• Fork the repository
• Create a feature branch (git checkout -b feature/amazing-feature)
• Commit your changes (git commit -m 'Add amazing feature')
• Push to the branch (git push origin feature/amazing-feature)
• Open a Pull Request

Development Guidelines

• Write TypeScript with proper type definitions
• Follow existing code style
• Add tests for new features
• Update documentation for API changes
• Ensure all tests pass before submitting PR

License

This project is licensed under the ISC License - see the LICENSE file for details.

Support

• Email: [e-mail]
• Issues: GitHub Issues
• Docs: Octokit Documentation
• Docs: Github REST API Documentation

Acknowledgments

• Built with H3ravel Musket
• Powered by Github
• Tunneling by ngrok (coming soon)

© Copyright 2026 - ToneFlix Technologies Limited