mirror of
https://github.com/MHSanaei/3x-ui.git
synced 2026-08-18 01:00:59 +00:00
Sanaei
8cec47a8a5
The three prompts still enforced the comment ban CLAUDE.md replaced with
the 2-line cap on Aug 1 (1ff90c5b), so the review bot would flag every
legitimate short comment; frontend/CLAUDE.md and CONTRIBUTING.md carried
the same stale rule. The PR reviewer's recipe for reading a post-change
file (headRefOid + pr diff) was unfulfillable with its allowlist - it now
fetches refs/pull/N/head and reads blobs via git show, object-only, no
checkout. Conventions the reviewer checks now include the unchecked docs
openapi.json copy step, the docs/lib/xray third link implementation, the
both-ways route contract, and the i18n dead-key half of the rule.
Also: drop the SUBPROCESS_ENV_SCRUB=0 override on the two untrusted-input
jobs (the mention job proves gh works scrubbed); teach the triage prompt
the issue forms (pre-applied labels, required fields, no re-asking); add
a security-report exception plus SECURITY.md so vulnerabilities are not
confirmed publicly; add a clarification follow-up job so a reporter's
reply to "clarification needed" is actually processed; review PRs again
on ready_for_review and skip drafts; stamp the reviewed head SHA so
force-pushes visibly date a review; scope gh issue/pr edit to label and
title flags; per-job concurrency; comment guards now match the actual
bot login after the run started; artifact names survive re-runs; the
mention prompt's repo map and env-var facts corrected (XUI_PORT,
XUI_TUNNEL_HEALTH_*, distro env files, memory.high, encrypt-tokens).
The bug and feature forms also referenced a "needs triage" label that
does not exist in the repo and was silently never applied - dropped.
103 lines
3.1 KiB
YAML
103 lines
3.1 KiB
YAML
name: Feature request
|
|
description: Suggest an idea or improvement for 3x-ui
|
|
title: "[Feature]: "
|
|
labels: ["enhancement"]
|
|
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
Thanks for taking the time to suggest a feature. Please **search
|
|
[existing issues](../issues?q=is%3Aissue)** first — duplicates will be closed.
|
|
|
|
- type: textarea
|
|
id: is-related-problem
|
|
attributes:
|
|
label: Is your feature request related to a problem?
|
|
description: A clear and concise description of the problem you're hitting today.
|
|
placeholder: I'm always frustrated when …
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: solution
|
|
attributes:
|
|
label: Describe the solution you'd like
|
|
description: |
|
|
What should the panel do? Be specific — UI placement, API shape,
|
|
config keys, expected behavior under edge cases.
|
|
placeholder: |
|
|
On the Inbounds page, add a button that …
|
|
The backend should expose a new endpoint at …
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: alternatives
|
|
attributes:
|
|
label: Alternatives you've considered
|
|
description: Other ways you tried to solve this, and why they fell short.
|
|
validations:
|
|
required: false
|
|
|
|
- type: textarea
|
|
id: use-case
|
|
attributes:
|
|
label: Concrete use case
|
|
description: |
|
|
Walk us through a real scenario where this feature would help.
|
|
Numbers help (e.g. "I manage 200 clients across 5 inbounds and …").
|
|
validations:
|
|
required: false
|
|
|
|
- type: textarea
|
|
id: mockup
|
|
attributes:
|
|
label: Mockups, screenshots, or examples
|
|
description: |
|
|
Drag images, paste config snippets, or link to similar features in
|
|
other tools. Helps us understand the shape of the request.
|
|
validations:
|
|
required: false
|
|
|
|
- type: dropdown
|
|
id: area
|
|
attributes:
|
|
label: Which parts of the panel would this affect?
|
|
multiple: true
|
|
options:
|
|
- Frontend (UI / panel pages)
|
|
- Backend (API endpoints, login, settings)
|
|
- Xray config generation
|
|
- Subscription (share links / Clash / JSON)
|
|
- Statistics / traffic counters
|
|
- Database / migrations
|
|
- Install / upgrade script
|
|
- Docker image
|
|
- Multi-node (sub-nodes)
|
|
- Telegram bot
|
|
- Other
|
|
validations:
|
|
required: false
|
|
|
|
- type: checkboxes
|
|
id: contribution
|
|
attributes:
|
|
label: Are you willing to help?
|
|
description: Optional — but maintainers prioritize requests with community help.
|
|
options:
|
|
- label: I'd like to implement this feature myself and open a PR.
|
|
required: false
|
|
- label: I can help test once a PR is open.
|
|
required: false
|
|
|
|
- type: checkboxes
|
|
id: checklist
|
|
attributes:
|
|
label: Before submitting
|
|
options:
|
|
- label: I searched [existing issues](../issues?q=is%3Aissue) and this feature has not been requested.
|
|
required: true
|
|
- label: This feature request is written in English.
|
|
required: true
|