Update name to gitlore instead of gitlab-inbox

This commit is contained in:
teernisse
2026-01-28 15:49:10 -05:00
parent 9a6357c353
commit 55b895a2eb
31 changed files with 1046 additions and 373 deletions

View File

@@ -25,46 +25,46 @@ If you aren't 100% sure how to use a third-party library, **SEARCH ONLINE** to f
---
## GitLab Inbox Robot Mode
## Gitlore Robot Mode
The `gi` CLI has a robot mode optimized for AI agent consumption with structured JSON output, meaningful exit codes, and TTY auto-detection.
The `lore` CLI has a robot mode optimized for AI agent consumption with structured JSON output, meaningful exit codes, and TTY auto-detection.
### Activation
```bash
# Explicit flag
gi --robot list issues
lore --robot list issues
# Auto-detection (when stdout is not a TTY)
gi list issues | jq .
lore list issues | jq .
# Environment variable
GI_ROBOT=1 gi list issues
LORE_ROBOT=true lore list issues
```
### Robot Mode Commands
```bash
# List issues/MRs with JSON output
gi --robot list issues --limit=10
gi --robot list mrs --state=opened
lore --robot list issues --limit=10
lore --robot list mrs --state=opened
# Count entities
gi --robot count issues
gi --robot count discussions --type=mr
lore --robot count issues
lore --robot count discussions --type=mr
# Show detailed entity info
gi --robot show issue 123
gi --robot show mr 456 --project=group/repo
lore --robot show issue 123
lore --robot show mr 456 --project=group/repo
# Check sync status
gi --robot sync-status
lore --robot sync-status
# Run ingestion (quiet, JSON summary)
gi --robot ingest --type=issues
lore --robot ingest --type=issues
# Check environment health
gi --robot doctor
lore --robot doctor
```
### Response Format
@@ -78,7 +78,7 @@ All commands return consistent JSON:
Errors return structured JSON to stderr:
```json
{"error":{"code":"CONFIG_NOT_FOUND","message":"...","suggestion":"Run 'gi init'"}}
{"error":{"code":"CONFIG_NOT_FOUND","message":"...","suggestion":"Run 'lore init'"}}
```
### Exit Codes
@@ -102,7 +102,7 @@ Errors return structured JSON to stderr:
### Best Practices
- Use `gi --robot` for all agent interactions
- Use `lore --robot` for all agent interactions
- Check exit codes for error handling
- Parse JSON errors from stderr
- Use `--limit` to control response size