jj-vcs/jj

docs: Make `jj log -T builtin_log_redacted` more visible for bug reports & other issues

Open

#9,372 opened on Apr 24, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (1,052 forks)batch import
documentation 📖good first issue

Repository metrics

Stars
 (28,830 stars)
PR merge metrics
 (Avg merge 23d 5h) (46 merged PRs in 30d)

Description

Ideally we update the GH bug report Template also to mention it.

This is a good task if you want to start to contribute to the project. The same issue also exists for the redacted operation log template, see builting_op_log_redacted.

What I mean by making it more visible:

  • Having an example output of it on the website and a general description of its use.
  • The docs for jj log also should mention the template explicitly for sharing

Contributor guide

Research direction
Update the GitHub bug report template to mention `jj log T builtin log redacted` and add documentation for the builtin log redacted template on the website and in the jj log command docs.
Tech stack
rust
Domain
cli
Issue type
Documentation
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.
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
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
95