Fix feature request title and description

This commit is contained in:
@starkos 2019-10-09 10:18:00 -04:00 committed by GitHub
parent ad89dfcb0d
commit f1bf795088
2 changed files with 22 additions and 28 deletions

View File

@ -1,28 +0,0 @@
---
name: Bug report
about: Create a report to help us improve
title: ''
labels: ''
assignees: ''
---
**What seems to be the problem?**
A clear and concise description of the bug.
**What did you expect to happen?**
A clear and concise description of what you expected to happen.
**What have you tried so far?**
Describe any steps you've taken to try to solve or workaround the bug.
**How can we reproduce this?**
Please provide a [minimal, reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) we can use to replicate the problem in our own development environments.
**What version of Premake are you using?**
`premake5 --version` will show you the version. If you are running a "-dev" version, please make sure you are up to date with the latest master branch.
**Anything else we should know?**
Add any other context about the problem here.
*You can now [support Premake on our OpenCollective](https://opencollective.com/premake). Your contributions help us spend more time responding to issues like these!*

View File

@ -0,0 +1,22 @@
---
name: Request a feature
about: Suggest a new feature or enhancement
title: ''
labels: enhancement
assignees: ''
---
**What problem will this solve?**
A clear and concise description of the problem this new feature is meant to solve, ex. "I'm always frustrated when [...]" or "Add support for this new toolset [...]". Please limit your request to a single feature; create multiple feature requests instead.
**What might be a solution?**
A clear and concise description of what you want to happen. If you are proposing changes to Premake's scripting APIs, provide an example of how your new feature might look when scripted. Use [code blocks](https://help.github.com/en/articles/creating-and-highlighting-code-blocks) to format your examples nicely.
**What other alternatives have you already considered?**
A clear and concise description of any alternative solutions or features you've considered.
**Anything else we should know?**
Add any other context or screenshots about the feature request here.
*(You can now [support Premake on our OpenCollective](https://opencollective.com/premake). Your contributions help us spend more time responding to requests like these!)*