[Preset Share] Tree-Structured Preset tailored for GitHub Bug Reports
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 82/100
Research direction
The body includes a complete preset and says to save it as issue-report.jsonc and run fastfetch.exe -c issue-report.jsonc. Start by checking the repository’s preset or configuration examples to see where community presets belong. Done means the preset is available in the project’s intended format and its command can load it.
Written by the indexing model from the issue text.
Description
Hey team,
Not a bug report or a feature request, just dropping a custom preset here since I wanted to share it with the community without going through the hassle of opening a formal PR.
I needed a fastfetch preset specifically designed to be pasted into GitHub issues and bug reports. The default templates are visually great for rice setups, but they seem too noisy for technical debugging—they expose local IPs, UI themes, window managers, and real-time metrics like uptime or used RAM that aren't relevant for static issue tracking.
This preset tries to fix that by offering:
-
Strict Separation: Hardware and Environment are isolated into two distinct blocks with ANSI-highlighted headers.
-
Zero PII & Noise: Stripped of IPs, uptime, theming things, dynamic percentages, etc.
-
Precise Storage Metrics: Separates physical drives (SSD/HDD, Fixed/Removable) from logical OS volumes and the Pagefile.
-
Tree Structure: Uses a fixed-width ASCII tree layout that renders fine inside GitHub markdown code blocks without alignment collision.
-
Future-Proof: Built using nominal variables instead of positional indexes.
Save it as issue-report.jsonc and run it with fastfetch.exe -c issue-report.jsonc.
{
"$schema": "https://github.com/fastfetch-cli/fastfetch/raw/dev/doc/json_schema.json",
"logo": {
"source": "",
"padding": {
"top": 1,
"right": 3
}
},
"display": {
"separator": ": ",
"key": {
"width": 16
},
"color": {
"keys": "38;5;39",
"separator": "38;5;240"
},
"size": {
"binaryPrefix": "jedec"
}
},
"modules": [
{
"type": "custom",
"format": "\u001b[1;38;5;45m┌── \u001b[1;38;5;16;48;5;45m HARDWARE \u001b[0m\u001b[1;38;5;45m ───────────────\u001b[0m"
},
{
"type": "board",
"key": "├─ Board"
},
{
"type": "bios",
"key": "├─ BIOS"
},
{
"type": "cpu",
"key": "├─ CPU",
"format": "{name} ({cores-physical} Cores / {cores-logical} Threads) @ {freq-max}"
},
{
"type": "gpu",
"key": "├─ GPU",
"format": "{name} @ {frequency} GHz"
},
{
"type": "physicalmemory",
"key": "├─ RAM"
},
{
"type": "physicaldisk",
"key": "├─ Storage",
"format": "{name} - {size} [{physical-type}, {removable-type}]"
},
{
"type": "monitor",
"key": "├─ Monitor",
"format": "{name} - {width}x{height} px @ {refresh-rate} Hz - {physical-width}x{physical-height} mm"
},
{
"type": "mouse",
"key": "├─ Mouse"
},
{
"type": "keyboard",
"key": "└─ Keyboard"
},
"break",
{
"type": "custom",
"format": "\u001b[1;38;5;45m┌── \u001b[1;38;5;16;48;5;45m ENVIRONMENT \u001b[0m\u001b[1;38;5;45m ────────────\u001b[0m"
},
{
"type": "os",
"key": "├─ OS"
},
{
"type": "kernel",
"key": "├─ Kernel"
},
{
"type": "title",
"key": "├─ User",
"format": "{user-name}@{host-name}"
},
{
"type": "locale",
"key": "├─ Locale"
},
{
"type": "disk",
"key": "├─ Volume",
"format": "[{mountpoint}] {size-total} - {filesystem}"
},
{
"type": "swap",
"key": "├─ Pagefile",
"format": "{total}"
},
{
"type": "shell",
"key": "├─ Shell"
},
{
"type": "terminal",
"key": "├─ Terminal"
},
{
"type": "vulkan",
"key": "├─ Vulkan"
},
{
"type": "opengl",
"key": "├─ OpenGL"
},
{
"type": "opencl",
"key": "└─ OpenCL"
},
"break"
]
}
EDIT: I made a few updates to include additional information, which are not shown in the screenshots below.
Screenshots
- Dominant language
- C
- Stars
- 25.4k
- Forks
- 947
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 21
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fastfetch-cli/fastfetch
-
[LOGO] VentoOSOpenlogo request
Difficulty 1/5 Under an hour Newbie friendliness 80/100
fastfetch-cli/fastfetch#2742 ·
Maintainers usually reply within 1 day
-
[LOGO] MacroMag OSPossibly taken @maldyrek claimed this 1 day ago. Openlogo request
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
fastfetch-cli/fastfetch#2740 ·
Maintainers usually reply within 1 day
-
logo request
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
fastfetch-cli/fastfetch#2713 · 1 comment ·
Maintainers usually reply within 1 day
-
[LOGO] Visnux LinuxPossibly taken @rafaelsoje claimed this 18 days ago. Openlogo request
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
fastfetch-cli/fastfetch#2700 ·
Maintainers usually reply within 1 day
-
[LOGO] ZelixOSPossibly taken @Hwi0228 claimed this 24 days ago. Openlogo request
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
fastfetch-cli/fastfetch#2685 · 1 comment ·
Maintainers usually reply within 1 day
All issues in fastfetch-cli/fastfetch
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
ecs_ptr_from_json does not free the buffer of a string longer than 256 bytes on two error pathsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SanderMertens/flecs#2444 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Cisco-Talos/clamav#1941 ·
Maintainers usually reply within 2 days