-
Notifications
You must be signed in to change notification settings - Fork 10
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
3 changed files
with
86 additions
and
35 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,37 +1,43 @@ | ||
name: Request a new feature | ||
description: File a feature request | ||
title: "[Tool, Solution, or Feature Name]: " | ||
title: "[Feature]: " | ||
labels: ["enhancement"] | ||
assignees: | ||
- octocat | ||
body: | ||
- type: markdown | ||
attributes: | ||
value: | | ||
Thanks for taking the time to fill out this feature request! | ||
Thanks for taking the time to help us improve! | ||
- type: textarea | ||
id: problem | ||
attributes: | ||
label: Is your feature request related to a problem? Please describe. | ||
description: A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] | ||
placeholder: Tell us what happened! | ||
value: "A problem occured!" | ||
label: Problem description | ||
description: Is your feature request related to a problem or challenge? Please describe what you are trying to do. | ||
placeholder: | | ||
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] | ||
(This section helps developers understand the context and *why* for this feature, in addition to the *what*) | ||
validations: | ||
required: false | ||
required: true | ||
- type: textarea | ||
id: solution | ||
attributes: | ||
label: Describe the solution you'd like. | ||
description: A clear and concise description of what you want to happen. | ||
placeholder: Tell us what you expect! | ||
value: "I want this feature!" | ||
label: Solution | ||
description: Tell us what you expect to happen. | ||
placeholder: A clear and concise description of what you want to happen. | ||
validations: | ||
required: true | ||
- type: textarea | ||
id: alternatives | ||
attributes: | ||
label: Alternative solutions | ||
description: Describe alternatives you've considered. | ||
placeholder: A clear and concise description of any alternative solutions or features you've considered. | ||
validations: | ||
required: false | ||
- type: checkboxes | ||
id: terms | ||
attributes: | ||
label: Code of Conduct | ||
description: By submitting this issue, you agree to follow our [Code of Conduct](https://example.com) | ||
description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/delta-incubator/delta-sharing-rs#coc-ov-file) | ||
options: | ||
- label: I agree to follow this project's Code of Conduct | ||
required: true |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
### Which issue does this PR close? | ||
|
||
<!-- | ||
We generally require a GitHub issue to be filed for all bug fixes and enhancements and this helps us generate change logs for our releases. You can link an issue to this PR using the GitHub syntax. For example `Closes #123` indicates that this PR will close issue #123. | ||
--> | ||
|
||
Closes #. | ||
|
||
### Rationale for this change | ||
|
||
<!-- | ||
Why are you proposing this change? If this is already explained clearly in the issue then this section is not needed. | ||
Explaining clearly why changes are proposed helps reviewers understand your changes and offer better suggestions for fixes. | ||
--> | ||
|
||
### Changes are included in this PR | ||
|
||
<!-- | ||
There is no need to duplicate the description in the issue here but it is sometimes worth providing a summary of the individual changes in this PR. | ||
--> | ||
|
||
### Are there any user-facing changes? | ||
|
||
<!-- | ||
If there are user-facing changes then we may require documentation to be updated before approving the PR. | ||
--> | ||
|
||
<!--- | ||
If there are any breaking changes to public APIs, please add the `breaking change` label. | ||
--> |