mirror of
https://github.com/nexu-io/open-design.git
synced 2026-06-01 03:14:35 +07:00
7d1adf9fd7
* docs: point 0.8.0 preview contributors at main, not preview/v0.8.0 0.8.0 has been merged into main (#1832). Anywhere we used to tell contributors to checkout / PR against preview/v0.8.0 was actively mis-routing new PRs. Update: - docs/preview-v0.8.0-announcement.md + zh-CN: status line, Branch row, source-build checkout, and 'open a PR against' guidance now point at main - .github/ISSUE_TEMPLATE/bug-report.yml + feature-request.yml: phrase the 'use the preview template' nudge as 'about the 0.8.0 preview features (now on main)' instead of 'about the preview/v0.8.0 branch' - .github/ISSUE_TEMPLATE/config.yml: same rewording for the contact link - .github/ISSUE_TEMPLATE/preview-v0.8.0-feedback.yml: refresh the description and the intro body so it reads as 'preview features pre-tag', not 'features pre-merge' The preview-v0.8.0-feedback template and preview/v0.8.0 label are intentionally kept: 0.8.0 isn't tagged yet, so we still want a dedicated lane for preview-features feedback. * chore: stop treating preview/v0.8.0 as a live branch Earlier in this PR we kept the preview-v0.8.0 surface area intact — that was the wrong call. 0.8.0 is now on main; pretending there's a parallel 'preview' branch in the templates, labels, and copy was going to keep mis-routing contributors. Drop: - .github/ISSUE_TEMPLATE/preview-v0.8.0-feedback.yml (the dedicated template that auto-applied the preview/v0.8.0 label and prefix) - .github/ISSUE_TEMPLATE/config.yml contact_links entry pointing at it - bug-report.yml + feature-request.yml nudges that sent users there - The Preview-v0.8.0-feedback link block from both announcement docs (replaced with normal bug-report / feature-request links) Rename: - docs/preview-v0.8.0-announcement.{md,zh-CN.md} -> docs/v0.8.0-announcement.{md,zh-CN.md} so the on-disk doc title reads as a 0.8.0 announcement, not a branch-specific one. No other repo file referenced the old paths. The preview/v0.8.0 label and branch themselves are intentionally untouched — those are separate ops the maintainer will decide on later. This PR only removes mentions inside the repo. * chore: keep 0.8.0 preview-feedback template as a chooser-level ad The previous commit deleted preview-v0.8.0-feedback.yml entirely. Bring it back, but reframe it: it's now the dedicated 0.8.0 lane in the issue chooser — a high-visibility surface that tells visitors "0.8.0 is here as a preview, please share what you noticed." - Renamed in the chooser to "Open Design 0.8.0 — preview feedback" - Title prefix shortened from "[preview/v0.8.0] " to "[0.8.0] " so the branch slug no longer leaks into issue titles - label preview/v0.8.0 still auto-applied (the label entity is still in use across 26 issues; maintainer will decide on its fate separately) - Area dropdown widened from "Skills + Automations" to cover the actual 0.8.0 surface (plugins, headless, agent flow, desktop shell) - Intro body rewritten to read as a preview-release ad, not a feature-branch tester request Announcement docs (English + Chinese) also routed their "open an issue" CTA back through this template instead of the generic bug-report / feature-request links — same advertising goal.
57 lines
2 KiB
YAML
57 lines
2 KiB
YAML
name: 💡 Feature request
|
|
description: Suggest a new feature or improvement for Open Design.
|
|
labels: ["enhancement"]
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
Thanks for sharing your idea!
|
|
|
|
Before you submit:
|
|
- Check whether the same idea is already discussed in [open issues](https://github.com/nexu-io/open-design/issues?q=is%3Aissue+label%3Aenhancement) or [Discussions → Ideas](https://github.com/nexu-io/open-design/discussions/categories/ideas).
|
|
- If you're still exploring an idea and want a conversation first, prefer [Discussions → Ideas](https://github.com/nexu-io/open-design/discussions/new?category=ideas).
|
|
|
|
- type: textarea
|
|
id: problem
|
|
attributes:
|
|
label: What problem are you trying to solve?
|
|
description: Describe the pain or limitation, not the solution. Why does today's behavior fall short?
|
|
placeholder: When I try to do X, the current flow forces me to ... which makes it hard to ...
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: solution
|
|
attributes:
|
|
label: Describe the solution you'd like
|
|
description: What's your proposed behavior, UI, or capability?
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: alternatives
|
|
attributes:
|
|
label: Alternatives you've considered
|
|
description: Other ways you've thought about solving this, and why they fall short.
|
|
placeholder: I also considered ... but it doesn't work because ...
|
|
validations:
|
|
required: false
|
|
|
|
- type: textarea
|
|
id: context
|
|
attributes:
|
|
label: Additional context
|
|
description: Screenshots, links to related issues, prior art in other tools, anything that helps.
|
|
validations:
|
|
required: false
|
|
|
|
- type: dropdown
|
|
id: contribution
|
|
attributes:
|
|
label: Would you be willing to contribute a PR?
|
|
options:
|
|
- "Yes, I can take this on"
|
|
- "Yes, with guidance from a maintainer"
|
|
- "No, just suggesting"
|
|
validations:
|
|
required: true
|