mongoose/.github/issue_template.md

- My goal is: _describe_
- My actions were: _describe_
- My expectation was: _describe_
- The result I saw: _provide logs or description_
- My question is: _your question_

# Environment

- mongoose version: _X.Y_
- Compiler/IDE and SDK: ZZZ version _X.Y_
- Target hardware/board: _?_
- Connectivity chip/module: _?_
- Target RTOS/OS (if applicable): _?_
Update issue template 2021-05-24 10:16:33 +01:00			`- My goal is: _describe_`
			`- My actions were: _describe_`
			`- My expectation was: _describe_`
			`- The result I saw: _provide logs or description_`
			`- My question is: _your question_`
Propose an issue template As it is in the discussion of raised issues to have some extra iteration because of architecture, library version, and other meta information, an issue template could save these extra rounds and possibly reduce the number of duplicates by highlighting where one can check for answers. This is just a sketch based on what notifications I got from mongoose in the past months. Feel free to change it. 2021-05-23 22:44:16 +02:00
Update issue template 2021-05-24 10:18:44 +01:00			`# Environment`
Propose an issue template As it is in the discussion of raised issues to have some extra iteration because of architecture, library version, and other meta information, an issue template could save these extra rounds and possibly reduce the number of duplicates by highlighting where one can check for answers. This is just a sketch based on what notifications I got from mongoose in the past months. Feel free to change it. 2021-05-23 22:44:16 +02:00
Update issue template 2021-11-25 11:47:26 +00:00			`- mongoose version: _X.Y_`
			`- Compiler/IDE and SDK: ZZZ version _X.Y_`
			`- Target hardware/board: _?_`
			`- Connectivity chip/module: _?_`
Update issue_template.md 2022-11-14 14:58:36 -03:00			`- Target RTOS/OS (if applicable): _?_`