rtk-ai/rtk

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

Open

#1,113 opened on Apr 9, 2026

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Rust (2,914 forks)batch import
area:clieffort-smallenhancementfilter-qualitygood first issuehelp wantedplatform:macospriority:low

Repository metrics

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

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

Research direction
Add a new config option `git.no merges` (default true) to control whether ` no merges` flag is passed to `git log`. Update the config parsing and the `git log` command invocation.
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.
2
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Rust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75