rtk-ai/rtk

Bug : New files added with `git add --intent-to-add` are omitted by `rtk git status`

Open

#1149 opened on Apr 10, 2026

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Rust (48,085 stars) (2,914 forks)batch import
bugeffort-smallfilter-qualitygood first issue

Description

When there is a new untracked file being git added with -N or --intent-to-add option, that file will have new file:

Reproduction steps

  • touch new_file
  • git add -N new_file
  • rtk git status -> sees clean - nothing to commit

Contributor guide

Tech stack
rust
Domain
clideveloper experience
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic Rust knowledgeFamiliarity with git internal commands
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Investigate the git status parsing logic in rtk. Locate where `rtk git status` processes the output of `git status`. Look for how new files are currently detected. The issue arises because files added with ` intent to add` appear as 'new file:' but are not handled. Check if there's a pattern matching on file statuses that excludes this case. Examine the relevant source file (likely in src/status.rs or similar) and consider adding a condition to include 'new file:' entries. Also review existing tests for git status to ensure coverage.