37 lines
1.8 KiB
YAML
37 lines
1.8 KiB
YAML
# Forgejo issue-template picker config.
|
|
#
|
|
# Forgejo reads this file to control what shows up when a user
|
|
# clicks "New Issue" on the repo. Together with the .md files in
|
|
# the same directory, this gives us:
|
|
#
|
|
# - A single "Bug report" template, auto-loaded into the comment
|
|
# field when the user picks it.
|
|
# - No "blank issue" escape hatch — testers cannot bypass the
|
|
# intake form by clicking "Don't see your issue here?". The
|
|
# bug_report.md template is the only path. This matters because
|
|
# §16 of the template contains the security-disclosure warning
|
|
# (and the operator's Matrix DM mxid); we want every reporter to
|
|
# see it before they post.
|
|
# - A contact link to the public community Matrix room so testers
|
|
# with questions / general comments / "is this a known issue?"
|
|
# can drop in there instead of opening an issue. The link is
|
|
# labelled community-chat, NOT security-disclosure: security
|
|
# disclosures go to the operator's DM mxid as documented in §16
|
|
# of the bug-report template, NOT to a public room. Putting the
|
|
# security-DM mxid on the picker UI would expose the operator's
|
|
# personal contact to anyone browsing the repo; putting the
|
|
# PUBLIC room on the picker UI would mis-route security bugs to
|
|
# a public channel. Splitting them this way solves both.
|
|
|
|
blank_issues_enabled: false
|
|
|
|
contact_links:
|
|
- name: "Community chat"
|
|
url: "https://matrix.to/#/#agorise:matrix.org"
|
|
about: |
|
|
Have a question, want to discuss something, or unsure whether
|
|
what you found is a real bug? Drop into the public Morphit
|
|
community Matrix room and ask first. (For SECURITY-SENSITIVE
|
|
issues — anything involving keys, funds, fee bypass, or
|
|
leaked private info — DO NOT post here either; the bug-report
|
|
template has the right private channel in section 16.)
|