Fix tea CLI syntax for viewing issues
The tea CLI doesn't have a `view` subcommand - use `tea issues <number>` directly instead of `tea issues view <number>`. - Fix example in ARCHITECTURE.md - Add clarifying tip in gitea skill to prevent this common mistake Closes #2 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit was merged in pull request #3.
This commit is contained in:
@@ -55,7 +55,7 @@ argument-hint: <issue-number>
|
|||||||
|
|
||||||
# Work on Issue #$1
|
# Work on Issue #$1
|
||||||
|
|
||||||
1. **View the issue**: `tea issue view $1`
|
1. **View the issue**: `tea issues $1`
|
||||||
2. **Create a branch**: `git checkout -b issue-$1-<title>`
|
2. **Create a branch**: `git checkout -b issue-$1-<title>`
|
||||||
...
|
...
|
||||||
```
|
```
|
||||||
|
|||||||
@@ -138,6 +138,7 @@ tea issues -r owner/repo # Specify repo directly
|
|||||||
|
|
||||||
## Tips
|
## Tips
|
||||||
|
|
||||||
|
- **View single issue**: Use `tea issues <number>` (NOT `tea issues view <number>` - there is no `view` subcommand)
|
||||||
- Always verify you're in the correct repository before running commands
|
- Always verify you're in the correct repository before running commands
|
||||||
- Use `tea issues` to find issue numbers before viewing/editing
|
- Use `tea issues` to find issue numbers before viewing/editing
|
||||||
- Reference issues in PR bodies with `Closes #N` for auto-linking
|
- Reference issues in PR bodies with `Closes #N` for auto-linking
|
||||||
|
|||||||
Reference in New Issue
Block a user