mirror of
https://github.com/nexu-io/open-design.git
synced 2026-06-01 03:14:35 +07:00
* 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.
91 lines
2.7 KiB
YAML
91 lines
2.7 KiB
YAML
name: 🧪 Open Design 0.8.0 — preview feedback
|
|
description: 0.8.0 is here as a preview on `main`. Bugs, suggestions, "this feels off", first impressions — drop them here.
|
|
labels: ["preview/v0.8.0"]
|
|
title: "[0.8.0] "
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
**Open Design 0.8.0 is shipping as a preview.** The rebuilt core (plugins, headless, agent-native) is on `main` and we're hardening it before tagging 0.8.0 stable.
|
|
|
|
This template is the fast lane for anything you noticed while trying 0.8.0 — bugs, UX rough edges, missing features, half-formed thoughts. Small reports are the most useful.
|
|
|
|
For issues that aren't about 0.8.0 specifically, the regular **Bug report** / **Feature request** templates still work fine.
|
|
|
|
- type: dropdown
|
|
id: feature
|
|
attributes:
|
|
label: Which area does this relate to?
|
|
options:
|
|
- Plugins / plugin authoring
|
|
- Skills tab (/integrations)
|
|
- Automations (Routines / Schedules / Live artifacts)
|
|
- Headless / CLI / agent-driven flow
|
|
- Desktop app shell
|
|
- General 0.8.0 experience
|
|
- Other / not sure
|
|
validations:
|
|
required: true
|
|
|
|
- type: dropdown
|
|
id: type
|
|
attributes:
|
|
label: Type of feedback
|
|
options:
|
|
- Bug / broken behavior
|
|
- UX or design concern
|
|
- Suggestion / feature request
|
|
- First impression / general thought
|
|
- Question
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: description
|
|
attributes:
|
|
label: What happened, or what would you like to see?
|
|
description: For bugs, include steps to reproduce. For suggestions, describe the use case.
|
|
placeholder: |
|
|
1. Open /integrations
|
|
2. Click the Skills tab
|
|
3. Expected X, saw Y
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: expected
|
|
attributes:
|
|
label: Expected behavior (skip if not a bug)
|
|
placeholder: What did you expect to happen?
|
|
validations:
|
|
required: false
|
|
|
|
- type: input
|
|
id: version
|
|
attributes:
|
|
label: Build / version
|
|
description: From the app's About menu, or run `git rev-parse HEAD` if you built from source.
|
|
placeholder: e.g. 0.8.0-preview.2
|
|
validations:
|
|
required: true
|
|
|
|
- type: dropdown
|
|
id: platform
|
|
attributes:
|
|
label: Platform
|
|
options:
|
|
- macOS (Apple Silicon)
|
|
- macOS (Intel)
|
|
- Windows
|
|
- Linux
|
|
- Other
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: context
|
|
attributes:
|
|
label: Additional context
|
|
description: Plugins installed, design systems in use, anything else relevant.
|
|
validations:
|
|
required: false
|