Two things on the new-issue page would have gone wrong for the first stranger to use it. The second contact link was named `No GitHub account? Report it in the #bugs forum instead`, unquoted. YAML reads ` #` as the start of a comment, so GitHub would have shown "No GitHub account? Report it in the" and nothing after it. The name is quoted now. The diagnostics and log fields said to attach a file, and both had `render:` set. GitHub turns attachments off on any textarea that renders, so the one required field asked for something it would not accept. Neither field renders now; the diagnostics block is markdown and reads fine as is, and the log field says to fence pasted lines. Also: the "not recognised? you are on 0.3.7" paragraph goes, since nobody outside ever ran 0.3.x; the Diagnostics page's save key is named for the PicoCalc too; Log detail is spelled the way the Preferences page shows it and says it needs a restart; the Cardputer leaves the placeholder, since nothing else mentions one. The pull-request template now states the same rule as CONTRIBUTING, and FUNDING points at Patreon's canonical /cw/ URL. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
16 lines
732 B
YAML
16 lines
732 B
YAML
blank_issues_enabled: false
|
|
contact_links:
|
|
- name: Not sure it's a bug? Ask on Discord
|
|
url: https://discord.gg/AZwe5Uvb3S
|
|
about: >
|
|
Setup trouble, "is it supposed to do this", or anything you want a second opinion
|
|
on. The #support forum is the place. Someone running your radio has probably hit it.
|
|
|
|
- name: "No GitHub account? Report it in the #bugs forum instead"
|
|
url: https://discord.gg/AZwe5Uvb3S
|
|
about: >
|
|
One post per bug, tagged, with the diagnostics file attached. Real ones get opened
|
|
here and your post is renamed with the issue number, so you can follow it without an
|
|
account — and something comes back to tell you when it ships. Being told beats
|
|
filing it tidily.
|