Skip to content

Commit efcb056

Browse files
committed
Revert "Update issue templates"
This reverts commit 455e428.
1 parent deccf9d commit efcb056

File tree

2 files changed

+108
-0
lines changed

2 files changed

+108
-0
lines changed
Lines changed: 87 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,87 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
<!-- Feel free to remove sections marked optional if they are not relevant. The other sections, please fill out. See also https://github.com/Mathics3/mathics-core/blob/master/REPORTING-BUGS.md -->
10+
11+
## Description
12+
13+
<!-- Please add a clear and concise description of the bug. Try to reduce the bug to the minimum expression that exhibits the bug.
14+
For example, if an expression occurs with several terms, can these be removed and the bug still appear? If so, we would like the reduced, simpler expression.
15+
16+
If the expression can be written in SymPy, does SymPy also exhibit the problem?
17+
-->
18+
19+
## How to Reproduce
20+
21+
<!--
22+
Steps to reproduce the behavior.
23+
24+
For Django:
25+
1. Go to ...
26+
2. Enter ....
27+
2. Click on ....
28+
3. Scroll down to '....'
29+
4. See error
30+
31+
For a command-line environment:
32+
33+
$mathics -c 'E ^ (Pi I)' # adjust expression E ^ (Pi I) for the specific bug
34+
35+
-->
36+
37+
## Output Given
38+
39+
<!--
40+
Please include not just the error message but all output leading to the message, which includes echoing input and messages up to the error.
41+
For a command-line environment, include the command invocation and all the output produced.
42+
43+
If this is too long, then try narrowing the problem to something short.
44+
-->
45+
46+
47+
## Expected behavior
48+
49+
<!-- Add a clear and concise description of what you expected to happen. -->
50+
51+
## Your Environment
52+
53+
<!--
54+
55+
Sometimes problems are specific to a particular environment or
56+
software release. If you have access to several environments, it is helpful to check whether this fails on more than one environment. Please
57+
indicate that when available.
58+
59+
If you are using a recently released Python package that Mathics3
60+
uses, it is possible we haven't tested this, and the new package is not
61+
compatible. Try on an older software release, and if that is still the problem, let us
62+
know about the breakage in the version.
63+
64+
In either case, please include the output from:
65+
66+
mathics --version
67+
68+
This information is also posted when you enter either the `mathics` or `mathicsscript` commands.
69+
70+
If you are running from a browser Django, please note the browser type, e.g., Firefox, Chrome, Safari.
71+
72+
Inside Django, http://localhost/about provides information, which you can cut and paste here.
73+
-->
74+
75+
## Workarounds
76+
77+
<!-- If there is a workaround for the problem, describe that here. -->
78+
79+
## Priority
80+
81+
<!-- If this is blocking some important activity, let us know what activity it blocks. -->
82+
83+
## Additional context
84+
85+
<!--
86+
This is optional. Please add any other context about the problem here or special environment setup.
87+
-->
Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
*Note: If the feature is about adding or filling out an existing deficiency in the Mathics3 language, please file this as an [issue](https://github.com/Mathics3/mathics-core/issues/new?assignees=&labels=&projects=&template=bug_report.md&title=).*
10+
11+
**Is your feature request related to a problem? Please describe.**
12+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
13+
14+
**Describe the solution you'd like**
15+
A clear and concise description of what you want to happen.
16+
17+
**Describe alternatives you've considered**
18+
A clear and concise description of any alternative solutions or features you've considered.
19+
20+
**Additional context**
21+
Add any other context or screenshots about the feature request here.

0 commit comments

Comments
 (0)