mirror of
				https://github.com/cmderdev/cmder.git
				synced 2025-10-31 09:22:15 +08:00 
			
		
		
		
	improvements to github form
This commit is contained in:
		
							
								
								
									
										21
									
								
								.github/ISSUE_TEMPLATE/feature-request.yml
									
									
									
									
										vendored
									
									
								
							
							
						
						
									
										21
									
								
								.github/ISSUE_TEMPLATE/feature-request.yml
									
									
									
									
										vendored
									
									
								
							| @@ -21,14 +21,14 @@ body: | ||||
|         - If you are opening the feature request regarding any of the **upstream technologies** that are used by Cmder, please open the feature request at the corresponding upstream repos instead: | ||||
|             - **[Clink](https://github.com/chrisant996/clink)**, the default shell in Cmder | ||||
|             - **[ConEmu](https://github.com/Maximus5/ConEmu)**, the terminal emulator | ||||
|             - **[Git/MinGW](https://github.com/git-for-windows/git), which also provide *NIX tools (such as `ls`, `mv`, `cp`, etc) | ||||
|             - **[Git/MinGW](https://github.com/git-for-windows/git)**, which also provide *NIX tools (such as `ls`, `mv`, `cp`, etc) | ||||
|             - **[clink-completions](https://github.com/repos/vladimir-kotikov/clink-completions)**, which provide autocompletion for clink | ||||
|  | ||||
|         - If you would like to ask for guides on how to integrate Cmder with your favorite IDE of choice, or how to perform a specific task with Cmder, make sure you visit our label section first. | ||||
|  | ||||
|           You may already have an answer under the Guides or Questions section. | ||||
|  | ||||
|           For a list of labels, visit **[🌐 Labels](https://github.com/cmderdev/cmder/labels). | ||||
|           For a list of labels, visit **[🌐 Labels](https://github.com/cmderdev/cmder/labels)**. | ||||
|  | ||||
|           (Be sure to also check “Closed” issues in the labels section!) | ||||
|  | ||||
| @@ -38,13 +38,6 @@ body: | ||||
|  | ||||
|         Thank you for making the Cmder project even better! ♥ | ||||
|  | ||||
|         ### Some tips on how to write a better feature request | ||||
|         - Make sure the description is worded well enough to be understood, and with as much context and examples as possible. | ||||
|         - Use the *Preview* tab to see how your issue will actually look like, before sending it. | ||||
|           ⚠ If for some reason you can not see the text you just wrote, make sure you've read the instructions clearly | ||||
|         - Please keep the ticket language to English only here. | ||||
|           We can't process your issue if it's written in Russian or Chinese as we can't understand them. | ||||
|  | ||||
|   - type: textarea | ||||
|     id: description | ||||
|     attributes: | ||||
| @@ -79,3 +72,13 @@ body: | ||||
|           required: true | ||||
|         - label: I have searched for similar issues and found none that describe my feature request. | ||||
|           required: true | ||||
|  | ||||
|   - type: markdown | ||||
|     attributes: | ||||
|       value: | | ||||
|         ### Some tips on how to write a better feature request | ||||
|         - Make sure the description is worded well enough to be understood, and with as much context and examples as possible. | ||||
|         - Use the *Preview* tab to see how your issue will actually look like, before sending it. | ||||
|           ⚠ If for some reason you can not see the text you just wrote, make sure you've read the instructions clearly | ||||
|         - Please keep the ticket language to English only here. | ||||
|           We can't process your issue if it's written in Russian or Chinese as we can't understand them. | ||||
|   | ||||
		Reference in New Issue
	
	Block a user