The README, CONTRIBUTING, SECURITY, the docs index, the development documents, the script READMEs, the comments of config.example.toml and pyproject.toml, and the issue and pull request forms. The legal sections of the README (attribution and licence) stay exactly as they were, between ste: off and ste: on markers. The SignPath attribution line, the one-line description of MeshTerm, every code block, and every URL do not change. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
31 lines
1.1 KiB
YAML
31 lines
1.1 KiB
YAML
name: Feature request
|
|
description: Suggest a feature or an improvement
|
|
labels: [enhancement]
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
One person works on MeshTerm in his spare time. For this reason, the honest answer to a
|
|
good idea is often "yes, but not soon". Tell us what you want to do, and not the
|
|
feature that you have in mind. Then we can often find a function that already works.
|
|
|
|
- type: textarea
|
|
id: problem
|
|
attributes:
|
|
label: What do you want to do
|
|
description: Describe your situation, and not the feature. What do you want to find out about your mesh?
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: idea
|
|
attributes:
|
|
label: What you had in mind
|
|
description: If you have an idea of the form, such as a screen, a key, or a subcommand, describe it.
|
|
|
|
- type: textarea
|
|
id: today
|
|
attributes:
|
|
label: What you do today instead
|
|
description: Describe the way around the problem, if there is one. This tells us more than anything else about how much the feature is worth.
|