forked from phoenix-oss/llama-stack-mirror
b84ab6c6b8
# What does this PR do? the `bug` and `enhancement` labels will be automatically applied to bugs and feature requests that are opened ## Test Plan N/A ## Sources https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository ## Before submitting - [ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case). - [x] Ran pre-commit to handle lint / formatting issues. - [x] Read the [contributor guideline](https://github.com/meta-llama/llama-stack/blob/main/CONTRIBUTING.md), Pull Request section? - [x] Updated relevant documentation. - [x] Wrote necessary unit or integration tests. Signed-off-by: Nathan Weinberg <nweinber@redhat.com>
28 lines
774 B
YAML
28 lines
774 B
YAML
name: 🚀 Feature request
|
|
description: Request a new llama-stack feature
|
|
labels: ["enhancement"]
|
|
body:
|
|
- type: textarea
|
|
id: feature-pitch
|
|
attributes:
|
|
label: 🚀 Describe the new functionality needed
|
|
description: >
|
|
A clear and concise description of _what_ needs to be built.
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: feature-motivation
|
|
attributes:
|
|
label: 💡 Why is this needed? What if we don't build it?
|
|
description: >
|
|
A clear and concise description of _why_ this functionality is needed.
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: other-thoughts
|
|
attributes:
|
|
label: Other thoughts
|
|
description: >
|
|
Any thoughts about how this may result in complexity in the codebase, or other trade-offs.
|