rtk-ai/rtk

`rtk git log` hides merge commits with no way to disable

Open

#1113 opened on Apr 9, 2026

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

Description

I regularly merge main into feature branches to keep them up to date. These merge commits are part of the branch history. Without them, the log is incomplete for AI agents.

Steps

  • rtk git log

Actual

rtk git log always injects --no-merges. Merge commits on the current branch are hidden from output.

Expected

Config option to include merge commits, e.g.:

[git]
no_merges = false

Environment

  • rtk 0.34.3
  • macOS 15.7.5

Contributor guide

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.
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 Rustunderstanding of CLI config
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Look for existing configuration struct (likely in src/config.rs or similar) and add a `no merges` boolean field. Then modify the git log command implementation (likely in src/commands/git.rs) to conditionally pass ` no merges` to git based on this config option. Follow the existing pattern for other git config options.