github issue templates - use comment blocks for instructions

As users sometimes tend not to remove the intsruction messages...
This commit is contained in:
Andrej730
2025-03-12 16:29:10 +05:00
parent e9a3d06352
commit 9be0a60c0a
2 changed files with 17 additions and 2 deletions
+11 -1
View File
@@ -7,14 +7,24 @@ assignees: ''
---
Replace this text describing what problem occurred and what you expected to happen instead.
**Error Description and Steps to Reproduce**
<!--
Describe what problem occurred and what you expected to happen instead.
1. To reproduce this, open file '...'
2. Click on '....'
3. See error
-->
**Attachments**
<!--
If applicable, add screenshots to help explain your problem. Please also drag-drop any files necessary to show the error (rename the file extension from .ifc to .txt to upload). Private files can be uploaded to https://ifcopenshell.org/upload.html - only viewed by core developers and will be deleted afterwards.
-->
**Debug information**
<!--
If this is in Bonsai, paste the output from the Copy Debug Information option in Bonsai. It can be found under Quality and Coordination -> Quality Control -> Debug. If this is a general software issue, if relevant include details about IfcOpenShell version, operating system, Python version, etc.
-->
+6 -1
View File
@@ -7,4 +7,9 @@ assignees: ''
---
Replace this text and describe a feature you'd like us to add. If it's not obvious, explain why this feature is awesome. Note that feature requests must be specific and measurable.
**Feature Description**
<!--
Describe a feature you'd like us to add. If it's not obvious, explain why this feature is awesome. Note that feature requests must be specific and measurable.
-->