grokkit/docs/user-guide/version.md
Greg Gauthier cd47686679
All checks were successful
CI / Test (pull_request) Successful in 42s
CI / Lint (pull_request) Successful in 27s
CI / Build (pull_request) Successful in 23s
docs: refactor README and docs structure for better organization
- Simplified README.md by moving detailed command docs, workflows, and development info to dedicated user-guide/ and developer-guide/ directories.
- Created index.md files for both guides to improve navigation.
- Extracted individual command guides (e.g., chat.md, edit.md) into user-guide/ for focused, maintainable documentation.
- Moved architecture, configuration, and troubleshooting to developer-guide/.
- Updated README links to point to the new docs structure.
2026-03-07 22:42:43 +00:00

22 lines
615 B
Markdown

# 🏷️ Version Guide
The `version` command prints the version, commit hash, and build date for the `grokkit` binary.
### Usage
```bash
grokkit version
```
### Output
```bash
grokkit version v0.1.0 (commit ab12cd3)
```
### Why use Version?
- **Troubleshooting**: When reporting an issue, providing the version helps maintainers identify the state of the code you are using.
- **Verification**: Confirm that you have successfully installed the latest version or that your local build is up-to-date.
- **Consistency**: Ensure all team members are using the same version of the tool for reproducible results.