diff options
author | Johnny Willemsen <jwillemsen@remedy.nl> | 2019-10-29 08:21:41 +0100 |
---|---|---|
committer | Johnny Willemsen <jwillemsen@remedy.nl> | 2019-10-29 08:21:41 +0100 |
commit | f8fdc53fe89ab445470b07b1379b18267f2f8c52 (patch) | |
tree | f819f00cfa13835f17fd6cdb7d8ca332b67d73ee /.github/ISSUE_TEMPLATE | |
parent | 1881b42c239c75498f75b0e14f71ebb5c5ec4b1d (diff) | |
download | ATCD-f8fdc53fe89ab445470b07b1379b18267f2f8c52.tar.gz |
Updated issue template to new github style
* .github/issue_template.md -> .github/ISSUE_TEMPLATE/bug_report.md:
Moved.
Diffstat (limited to '.github/ISSUE_TEMPLATE')
-rw-r--r-- | .github/ISSUE_TEMPLATE/bug_report.md | 54 |
1 files changed, 54 insertions, 0 deletions
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md new file mode 100644 index 00000000000..66493f4d26d --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -0,0 +1,54 @@ +--- +name: Bug report +about: Create a report to help us improve +title: '' +labels: '' +assignees: '' + +--- + +### Version + +The version of ACE and/or TAO you are using + +### Host machine and operating system + +### Target machine and operating system (if different from host) + +### Compiler name and version (including patch level) + +### The $ACE_ROOT/ace/config.h file + +If you use a link to a platform-specific file, simply state which one + +### The $ACE_ROOT/include/makeinclude/platform_macros.GNU file + +if you use a link to a platform-specific file, simply state which one (unless this isn't used in this case, e.g., with Microsoft Visual C++) + +### Contents of $ACE_ROOT/bin/MakeProjectCreator/config/default.features + +Used by MPC when you generate your own makefiles + +### AREA/CLASS/EXAMPLE AFFECTED: + +What example failed? What module failed to compile? + +### The problem effects: + +Does it affect compilation, linking, or execution. Please indicate whether ACE/TAO, your application, or both are affected. + +### Synopsis + +Brief description of the problem + +### Description + +Detailed description of problem. Don't just say "<blah> doesn't work, here's a fix," explain what your program does to get to the <blah> state. + +### Repeat by + +What you did to get the error; include test program or session transcript if at all possible. + +### Sample fix/ workaround + +If available |