Browse Source

Update feature_request.

Jon Shier 4 years ago
parent
commit
fae9005e09
1 changed files with 18 additions and 15 deletions
  1. 18 15
      .github/ISSUE_TEMPLATE/feature_request.md

+ 18 - 15
.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,20 +1,23 @@
----
-name: Feature request
-about: Suggest an idea for this project
-title: ''
-labels: ''
-assignees: ''
+> ℹ Please fill out this template when filing a feature request.
+> All lines beginning with an ℹ symbol instruct you with what info we expect. You can delete those lines once you've filled in the info.
+>
+> Feature requests should code examples whenever possible.
+>
+> Per our [*CONTRIBUTING guidelines](https://github.com/Alamofire/Alamofire/blob/master/CONTRIBUTING.md), we use GitHub for
+> bugs and feature requests, not general support. Other issues should be opened on Stack Overflow with the tag `alamofire`.
+>
+> Please remove this line and everything above it before submitting.
 
----
+* [ ] I've read, understood, and done my best to follow the [*CONTRIBUTING guidelines](https://github.com/Alamofire/Alamofire/blob/master/CONTRIBUTING.md).
 
-**Is your feature request related to a problem? Please describe.**
-A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+## Problem
 
-**Describe the solution you'd like**
-A clear and concise description of what you want to happen.
+ℹ Please replace this with a summary of the problem you're trying to solve.
 
-**Describe alternatives you've considered**
-A clear and concise description of any alternative solutions or features you've considered.
+## Feature Request
 
-**Additional context**
-Add any other context or screenshots about the feature request here.
+ℹ Please replace this with a summary of the feature you're requesting.
+
+## Value to Alamofire
+
+ℹ Please replace this with a summary of why you think this is something Alamofire should have, rather than it existing in your codebase or as a separate library.