You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/bug_report.md
+12-22Lines changed: 12 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,32 +7,22 @@ assignees: ''
7
7
8
8
---
9
9
10
-
**Describe the bug**
10
+
## Describe the bug
11
11
A clear and concise description of what the bug is.
12
12
13
-
**To Reproduce**
14
-
Steps to reproduce the behavior:
15
-
1. Go to '...'
16
-
2. Click on '....'
17
-
3. Scroll down to '....'
18
-
4. See error
13
+
## To Reproduce
14
+
Steps to reproduce the behavior. This can be in the form of a code snippet or some config files or a notebook to produce a minimum viable example of the bug.
19
15
20
-
**Expected behavior**
21
-
A clear and concise description of what you expected to happen.
16
+
## Expected behavior
17
+
A clear and concise description of what you expect(ed) to happen.
22
18
23
-
**Screenshots**
19
+
## Screenshots
24
20
If applicable, add screenshots to help explain your problem.
25
21
26
-
**Desktop (please complete the following information):**
27
-
- OS: [e.g. iOS]
28
-
-Browser [e.g. chrome, safari]
29
-
- Version [e.g. 22]
22
+
## Environment (please complete the following information)
23
+
- OS: [e.g. MacOS]
24
+
-Python Version: [e.g. 3.8]
25
+
-`c3-toolset`Version [e.g. 1.2]
30
26
31
-
**Smartphone (please complete the following information):**
32
-
- Device: [e.g. iPhone6]
33
-
- OS: [e.g. iOS8.1]
34
-
- Browser [e.g. stock browser, safari]
35
-
- Version [e.g. 22]
36
-
37
-
**Additional context**
38
-
Add any other context about the problem here.
27
+
## Additional context
28
+
Add any other context about the problem here. You can also suggest possible solutions and relevant implementations & edge case details.
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/feature_request.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,14 +7,14 @@ assignees: ''
7
7
8
8
---
9
9
10
-
**Is your feature request related to a problem? Please describe.**
11
-
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
10
+
## Describe the missing feature
11
+
A clear and concise description of what the problem is and what is being missed. Ex. I'm always frustrated when [...]
12
12
13
-
**Describe the solution you'd like**
14
-
A clear and concise description of what you want to happen.
13
+
## Describe the solution you'd like
14
+
A clear and concise description of what you want to happen. If possible, provide example input-output descriptions or usecases. Better still, consider providing code snippets that outline the expected behaviour. Ex. I would like to call [...] on the [...] class objects to get [...] done.
15
15
16
-
**Describe alternatives you've considered**
17
-
A clear and concise description of any alternative solutions or features you've considered.
16
+
## Describe alternatives you've considered
17
+
How have you tried to resolve it in the current version of the code? Have you considered non `c3-toolset` alternative solutions? Please elaborate.
18
18
19
-
**Additional context**
20
-
Add any other context or screenshots about the feature request here.
19
+
## Additional context
20
+
Add any other context or screenshots about the feature request here. Please feel free to suggest details about how you believe this feature request might be best implemented. If you have used similar features in other libraries, consider providing links or resources to example implementations.
Describe very concisely what this Pull Request does.
3
+
4
+
## Why
5
+
Describe what motivated this Pull Request and why this was necessary. Use closing keywords to link to the relevant Issue. Ex. Closes #666
6
+
7
+
## How
8
+
Describe details of how you implemented the solution, outlining the major steps involved in adding this new feature or fixing this bug. Provide code-snippets if possible, showing example usage.
9
+
10
+
## Remarks
11
+
Add notes on possible known quirks/drawbacks of this solution. If this introduces an API-breaking change, please provide an explanation on why it is necessary to break API compatibility and how users should update their notebook/script workflows once this PR is merged.
12
+
13
+
## Checklist
14
+
Please include and complete the following checklist. Your Pull Request is (in most cases) not ready for review until the following have been completed. You can create a draft PR while you are still completing the checklist. Check the [Contribution Guidelines](https://github.com/q-optimize/c3/blob/dev/CONTRIBUTING.md) for more details. You can mark an item as complete with the `- [x]` prefix
15
+
16
+
-[ ] Tests - Added unit tests for new code, regression tests for bugs and updated the integration tests if required
17
+
-[ ] Formatting & Linting - `black` and `flake8` have been used to ensure styling guidelines are met
18
+
-[ ] Type Annotations - All new code has been type annotated in the function signatures using type hints
19
+
-[ ] Docstrings - Docstrings have been provided for functions in the `numpydoc` style
20
+
-[ ] Documentation - The tutorial style documentation has been updated to explain changes & new features
21
+
-[ ] Notebooks - Example notebooks have been updated to incorporate changes and new features
22
+
-[ ] Changelog - A short note on this PR has been added to the Upcoming Release section
0 commit comments