ISSUE: does not understand and handle dbt, bq, and some git commands
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 81.1k
- Forks
- 5.1k
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 35
Description
TOP UNHANDLED COMMANDS -- open an issue?
Command Count Example
bq query 559 bq query --nouse_legacy_sql --max_rows..
dbt compile 83 /Users/xxx/xx/GitHub/xxx-xxx..
python 53 /Users/xxx/xx/GitHub/xxx-xxx..
python3 51 python3 - << 'EOF'
import yaml
with o..
Check 50 # Check what sources are defined in sc..
git checkout 49 git checkout develop
dbt run 45 dbt run --full-refresh --profiles-dir ..
bq show 24 bq show --format=prettyjson --project_..
cat 24 cat > /Users/xxxx/xxx/GitHub/d..
bq ls 24 bq ls --format=json xxxx
git mv 23 git mv xxxx..
python3 << 19 BASE=/Users/xxx/xxx/GitHub/da..
git ls-files 14 git -C /Users/xxx/xxxx/GitHub/..
The 13 # The directory is itself a symlink lo..
for f 11 BASE=/Users/xxx/xxx/GitHub/da..
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue lists unhandled bq, dbt, Python, and git commands for the Rust CLI, but names no source files or tests. Start by finding where the CLI recognizes existing commands and compare that behavior with the listed examples. Done means the identified commands are handled without being reported as unhandled, with coverage for the relevant cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python, rust
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100