Switch Angular from hash-based to path-based routing so each Wails window (/tray, /main, /settings) loads its correct route. Archive GitHub Actions workflows to .gh-actions/, update Forgejo deploy registry to dappco.re/osi, and apply gofmt/alignment fixes across packages. Co-Authored-By: Virgil <virgil@lethean.io>
58 lines
1.4 KiB
YAML
58 lines
1.4 KiB
YAML
name: Feature Request
|
|
description: Suggest a new feature or enhancement
|
|
title: "[Feature]: "
|
|
labels: ["enhancement"]
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
Thanks for the suggestion! Please describe your idea below.
|
|
|
|
- type: dropdown
|
|
id: area
|
|
attributes:
|
|
label: Area
|
|
options:
|
|
- dev commands (work, commit, push, pull)
|
|
- php commands (test, lint, stan)
|
|
- GitHub integration (issues, reviews, ci)
|
|
- New command
|
|
- Documentation
|
|
- Other
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: problem
|
|
attributes:
|
|
label: Problem or use case
|
|
description: What problem does this solve?
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: solution
|
|
attributes:
|
|
label: Proposed solution
|
|
description: How would you like it to work?
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: alternatives
|
|
attributes:
|
|
label: Alternatives considered
|
|
description: Any other approaches you've thought about?
|
|
|
|
- type: dropdown
|
|
id: complexity
|
|
attributes:
|
|
label: Estimated complexity
|
|
description: How much work do you think this requires?
|
|
options:
|
|
- "Small - Quick fix, single file, < 1 hour"
|
|
- "Medium - Multiple files, few hours to a day"
|
|
- "Large - Significant changes, multiple days"
|
|
- "Unknown - Not sure"
|
|
validations:
|
|
required: false
|