jj-vcs/jj

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

Open

#9372 opened on Apr 24, 2026

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

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

Tech stack
rust
Domain
documentation
Issue type
documentation
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.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic knowledge of jjability to edit markdown
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
First, examine the current GitHub bug report template in the repository (likely in .github/ISSUE TEMPLATE) to add a note about using `jj log T builtin log redacted`. Then, review the documentation for `jj log` in the project's website (e.g., docs/ directory) to add an explicit mention of the template and include an example output. Also consider adding a general description of the template's use on the website. The same should be done for the `builtin op log redacted` template as mentioned in the issue.