From 30c3c2f4d867e8497e49175df10a55a7115da700 Mon Sep 17 00:00:00 2001 From: root Date: Thu, 2 Jul 2026 00:06:39 +0200 Subject: [PATCH] docs(issues): add YAML issue forms (bug, feature) + config - .forgejo/ISSUE_TEMPLATE/bug.yml - .forgejo/ISSUE_TEMPLATE/feature.yml - .forgejo/ISSUE_TEMPLATE/config.yml: blank_issues_enabled=false, contact_links to discussions (Q&A, Feature Requests, Announcements) Discussions per repo land in a separate follow-up commit. --- .forgejo/ISSUE_TEMPLATE/bug.yml | 86 +++++++++++++++++++++++++++++ .forgejo/ISSUE_TEMPLATE/config.yml | 11 ++++ .forgejo/ISSUE_TEMPLATE/feature.yml | 83 ++++++++++++++++++++++++++++ 3 files changed, 180 insertions(+) create mode 100644 .forgejo/ISSUE_TEMPLATE/bug.yml create mode 100644 .forgejo/ISSUE_TEMPLATE/config.yml create mode 100644 .forgejo/ISSUE_TEMPLATE/feature.yml diff --git a/.forgejo/ISSUE_TEMPLATE/bug.yml b/.forgejo/ISSUE_TEMPLATE/bug.yml new file mode 100644 index 0000000..00b60d2 --- /dev/null +++ b/.forgejo/ISSUE_TEMPLATE/bug.yml @@ -0,0 +1,86 @@ +name: Bug Report +description: Report a defect or unexpected behavior +title: "[Bug]: " +labels: ["bug", "triage"] +body: + - type: markdown + attributes: + value: | + Thanks for reporting a bug. Please fill in the sections below. + + - type: input + id: version + attributes: + label: Version + description: Tag, branch, or commit SHA where the bug reproduces + placeholder: "v1.2.3 or main@abc1234" + validations: + required: true + + - type: dropdown + id: severity + attributes: + label: Severity + description: How bad is the impact? + options: + - Critical (data loss, security, total outage) + - High (major feature broken, no workaround) + - Medium (feature broken, workaround exists) + - Low (minor, cosmetic) + validations: + required: true + + - type: textarea + id: summary + attributes: + label: What happened? + description: Clear, factual description of the bug + placeholder: | + Expected: ... + Actual: ... + validations: + required: true + + - type: textarea + id: repro + attributes: + label: Steps to reproduce + description: Numbered steps. Include URLs, commands, inputs. + placeholder: | + 1. Go to /scanner/scan + 2. Enter address 0x... + 3. Click "Analyze" + 4. See "undefined" instead of risk score + render: shell + validations: + required: true + + - type: textarea + id: logs + attributes: + label: Logs / errors / stack trace + description: Paste relevant output. Use a code block. + render: shell + placeholder: | + ``` + 2026-07-02T10:00:00 ERROR ... + ``` + + - type: input + id: env + attributes: + label: Environment + description: OS, browser, runtime version, etc. + placeholder: "macOS 14.5, Chrome 125, Node 22.3" + + - type: checkboxes + id: checks + attributes: + label: Pre-submit checks + options: + - label: I searched existing issues and didn't find a duplicate + required: true + - label: I can reproduce this on `main` HEAD + required: false + - label: I'm willing to submit a PR + required: false diff --git a/.forgejo/ISSUE_TEMPLATE/config.yml b/.forgejo/ISSUE_TEMPLATE/config.yml new file mode 100644 index 0000000..bb56525 --- /dev/null +++ b/.forgejo/ISSUE_TEMPLATE/config.yml @@ -0,0 +1,11 @@ +blank_issues_enabled: false +contact_links: + - name: Q&A + url: https://git.rugmunch.io/RugMunchMedia/rmi-backend/discussions/new?category=q-a + about: Use this for questions and troubleshooting + - name: Feature Requests + url: https://git.rugmunch.io/RugMunchMedia/rmi-backend/discussions/new?category=feature-requests + about: Suggest a new feature or improvement (preview / brainstorm) + - name: Announcements + url: https://git.rugmunch.io/RugMunchMedia/rmi-backend/discussions/new?category=announcements + about: Stay up to date on releases and changes diff --git a/.forgejo/ISSUE_TEMPLATE/feature.yml b/.forgejo/ISSUE_TEMPLATE/feature.yml new file mode 100644 index 0000000..c9b206d --- /dev/null +++ b/.forgejo/ISSUE_TEMPLATE/feature.yml @@ -0,0 +1,83 @@ +name: Feature Request +description: Propose a new feature or improvement +title: "[Feature]: " +labels: ["enhancement", "triage"] +body: + - type: markdown + attributes: + value: | + Use this for new features or improvements. For bugs, use the Bug Report template. + + - type: dropdown + id: area + attributes: + label: Area + description: Which product / surface does this affect? + options: + - RMI (scanner / dashboard) + - Pry (crawler) + - WalletPress + - RugCharts + - RugMaps + - x402 Gateway + - Infra / CI / tooling + - Other + validations: + required: true + + - type: textarea + id: problem + attributes: + label: Problem / motivation + description: What user pain or gap does this address? Why is it worth building? + placeholder: | + As a , I want to , so that . + validations: + required: true + + - type: textarea + id: proposal + attributes: + label: Proposed solution + description: How would you build it? API, UI, data model. + placeholder: | + - Add new endpoint POST /api/v1/... + - Add new column `risk_score` to `tokens` table + - Add new React component `RiskBadge` + + - type: textarea + id: alternatives + attributes: + label: Alternatives considered + description: Other ways to solve this. Why this approach? + + - type: textarea + id: scope + attributes: + label: Acceptance criteria + description: How do we know it's done? Checklist. + placeholder: | + - [ ] Endpoint returns + - [ ] Tests cover happy + edge cases + - [ ] Docs updated + - [ ] No new lint errors + + - type: checkboxes + id: effort + attributes: + label: Effort estimate + options: + - Small (< 1 day) + - Medium (1-3 days) + - Large (1-2 weeks) + - XL (2+ weeks, breaking change) + + - type: checkboxes + id: checks + attributes: + label: Pre-submit checks + options: + - label: I searched existing issues and didn't find a duplicate + required: true + - label: I'm willing to submit a PR + required: false