jj-vcs/jj

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

Open

#9,372 建立於 2026年4月24日

在 GitHub 查看
 (1 留言) (0 反應) (0 負責人)Rust (28,830 star) (1,052 fork)batch import
documentation 📖good first issue

描述

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

貢獻者指南

技術棧
rust
領域
documentation
議題類型
documentation
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
basic knowledge of jjability to edit markdown
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
80
研究方向
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.