`tracker list` leaves out trackers with no `paths`
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
Research direction
Start at the implementation of newgit tracker list and inspect how it selects trackers and formats the PATHS column. Compare a tracker with paths = [] against one with paths, then check the existing wording referenced in issue #44 and the supabase template example. Done means all trackers appear, with deposit or resource information shown for trackers without paths; verify the ROLE column also includes roles from those trackers.
Written by the indexing model from the issue text.
Description
newgit tracker list leaves out every tracker with paths = []. In a project with runtime-env (six paths) and branch-db (paths = [], resources = ["db", "functions"], deposits from db):
NAME KIND ROLE STORAGE AUDIENCE PATHS
root code - local project-devs (everything no other tracker claims)
project code - local project-devs .newgit
access code - local project-devs (maintained by owner) .newgit/trackers
runtime-env secret - local user apps/admin/.env.local, ...
branch-db isn't listed, although spawn --use branch-db binds it and status shows it. The same happened with two role alternatives (shared-db and branch-db, role db): neither showed, so the ROLE column never shows the one role the project has.
A deposit-only tracker or one that only brings resources is a normal thing to define (the supabase template creates one), and the list is where you'd check what --use accepts.
Expected: list every tracker, with something like (deposits only) or brings: db, functions in PATHS. See also the (0 files) wording from #44.
Environment: newgit 0.7.0 (06fc371005bc), macOS (Darwin 27.0.0), git 2.55.0, Supabase CLI 2.108.0, Docker 29.9.2. npm-workspaces monorepo (Expo + Next.js + Supabase); resources deps (install), admin (process), db (supabase), functions (process).
- Dominant language
- Rust
- Stars
- 0
- Forks
- 0
- Avg merge
- 4h 56m
- Merged PRs (30d)
- 51
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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.
More from Spheroman/newgit
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Port allocation order within a resource is unspecifiedPossibly taken A pull request linked to this issue is open or already merged. Opendocumentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Spheroman/newgit#59 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
All issues in Spheroman/newgit
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
BurntSushi/jiff#668 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
router-for-me/EasyCLIProxyAPI#534 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
astral-sh/astral-codec#244 ·
Maintainers usually reply within 1 day
-
ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug dependencies kind:fix priority: P3 ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
shep-pm/shep#1318 · 1 comment ·
Maintainers usually reply within 1 day