rtk-ai/rtk

Add rtk git rev-parse passthrough

Open

#1,729 opened on May 5, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (2,914 forks)batch import
area:clienhancementhelp wantedpriority:low

Repository metrics

Stars
 (48,085 stars)
PR merge metrics
 (Avg merge 11d 1h) (45 merged PRs in 30d)

Description

Problem

67 invocations of git rev-parse in 30 days, mostly:

  • git rev-parse --show-toplevel
  • git rev-parse HEAD
  • git rev-parse --abbrev-ref HEAD

These are already minimal output (one line), so there's nothing to compress — but they're not currently routed through rtk git, so they don't show up in rtk gain analytics and break the "everything git goes through rtk" mental model.

Proposal

Add rev-parse to the rtk git passthrough list. No filtering needed — just route it so usage is tracked and behavior is consistent with the rest of the git * family.

Low effort, mostly hygiene.

Contributor guide

Research direction
Look at existing git passthroughs in the codebase (e.g., git status, git log) and add rev parse similarly. Ensure routing is consistent.
Tech stack
rust
Domain
cli
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
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
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80