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
+19-4Lines changed: 19 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,14 @@
1
+
---
2
+
name: Bug report
3
+
about: Create a report to help us improve
4
+
title: ''
5
+
labels: bug
6
+
assignees: ''
7
+
8
+
---
9
+
1
10
<!--
2
-
If you want to report a bug, we added some points below you can fill out. If you want to request a feature, feel free to remove all the irrelevant text. In addition to this [issue tracker](https://github.com/diesel-rs/diesel/issues), you can also talk to Diesel maintainers and users on [Gitter](https://gitter.im/diesel-rs/diesel).
11
+
If you want to report a bug, we added some points below which help us track down the problem faster.
3
12
-->
4
13
5
14
## Setup
@@ -33,16 +42,22 @@ If you want to report a bug, we added some points below you can fill out. If you
33
42
### Steps to reproduce
34
43
35
44
<!--
36
-
Please include as much of your codebase as needed to reproduce the error. If the relevant files are large, please consider linking to a public repository or a [Gist](https://gist.github.com/).
45
+
Please include as much of your codebase as needed to reproduce the error. If the relevant files are large, please consider linking to a public repository or a [Gist](https://gist.github.com/). This includes normally the following parts:
37
46
38
-
Please post as much of your database schema as necessary. If you are using `infer_schema!`, you can use `diesel print-schema` and post the relevant parts from that.
47
+
* The exact code where your hit the problem
48
+
* Relevant parts your schema, so any `table!` macro calls required for the
49
+
* Any other type definitions involved in the code, which produces your problem
39
50
-->
40
51
41
52
## Checklist
42
53
43
-
-[ ] I have already looked over the [issue tracker](https://github.com/diesel-rs/diesel/issues) for similar issues.
54
+
-[ ] I have already looked over the [issue tracker](https://github.com/diesel-rs/diesel/issues) and the [disussion forum](https://github.com/diesel-rs/diesel/discussions) for similar possible closed issues.
55
+
<!--
56
+
If you are unsure if your issue is a duplicate of an existing issue please link the issue in question here
57
+
-->
44
58
-[ ] This issue can be reproduced on Rust's stable channel. (Your issue will be
45
59
closed if this is not the case)
60
+
-[ ] This issue can be reproduced without requiring a third party crate
46
61
47
62
<!--
48
63
Thank you for your submission! You're helping make Diesel more robust 🎉
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+10-8Lines changed: 10 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,17 +36,19 @@ Thank you! We'll try to respond as quickly as possible.
36
36
37
37
## Submitting feature requests
38
38
39
-
If you can't find an issue (open or closed) describing your idea on our [issue
40
-
tracker], open an issue. Adding answers to the following
41
-
questions in your description is +1:
39
+
Diesel's issue tracker is meant to represent our current roadmap. An open issue represents either a bug, or a new feature that a member of the Diesel team is actively working on.
42
40
43
-
- What do you want to do, and how do you expect Diesel to support you with that?
44
-
- How might this be added to Diesel?
45
-
- What are possible alternatives?
46
-
- Are there any disadvantages?
41
+
This means that you should not submit a feature request to our issue tracker, unless you were asked to do so by a member of the Diesel team. Feature requests should instead be posted in
0 commit comments