Files
tty7/.github/ISSUE_TEMPLATE/bug.yml
T
l0ng-ai 5542fd5e12 docs(issues): say the bug template's log needs TTY7_LOG (#1017)
tty7.log is only written when TTY7_LOG is set, so reporters following
the template find no file (#1010). Say how to turn it on, and ask for
crash.log, which is always written.

Claude-Session: https://claude.ai/code/session_01JRqYZ9E153WpSHGS2AW3BM
2026-09-29 19:32:03 +08:00

93 lines
2.5 KiB
YAML

name: Bug report
description: Something in tty7 doesn't work as expected
labels: ["bug"]
body:
- type: checkboxes
id: checks
attributes:
label: Before you file
options:
- label: I searched the existing issues and this isn't a duplicate.
required: true
- label: I'm on the latest tty7 release, or I've said below why I can't be.
required: true
- type: textarea
id: summary
attributes:
label: What happened?
description: The behaviour you saw, in a sentence or two.
validations:
required: true
- type: textarea
id: repro
attributes:
label: Steps to reproduce
description: >
Numbered steps starting from a freshly opened tty7 window. If a
specific command or escape sequence triggers it, paste the exact one —
"some TUI app" is rarely enough to reproduce a terminal bug.
placeholder: |
1. Open a new tab
2. Run `printf '\e[?2004h'`
3. Type a character — the pane freezes
validations:
required: true
- type: textarea
id: expected
attributes:
label: What did you expect instead?
validations:
required: true
- type: input
id: version
attributes:
label: tty7 version
description: Run `tty7 --version`, or check the About window.
placeholder: "26.9.2"
validations:
required: true
- type: dropdown
id: platform
attributes:
label: Platform
options:
- macOS (Apple Silicon)
- macOS (Intel)
- Windows
- Linux
validations:
required: true
- type: input
id: context
attributes:
label: Shell and TUI app involved
description: >
The shell you were running, and the TUI app plus its version if one is
on screen when it happens.
placeholder: fish 3.7.1, neovim 0.10.2
- type: textarea
id: logs
attributes:
label: Log output
description: >
tty7 only writes a log when `TTY7_LOG` is set (e.g. `TTY7_LOG=debug`),
so there is none by default: set it, quit tty7 completely, reproduce,
then paste the tail of `~/.config/tty7/tty7.log`
(`%APPDATA%\tty7\tty7.log` on Windows). After a crash, include
`crash.log` from the same folder — that one is always written. This is
rendered as code, so no backticks needed.
render: shell
- type: textarea
id: extra
attributes:
label: Anything else?
description: Screenshots, a recording, or anything else worth knowing.