Skip to content

Commit 1580ed3

Browse files
caffeine-addicttcaffeine-addictt
committed
+ Added issue templates
1 parent ec9d69b commit 1580ed3

File tree

4 files changed

+242
-0
lines changed

4 files changed

+242
-0
lines changed

‎.github/ISSUE_TEMPLATE/1-bug-report.md

Lines changed: 82 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,82 @@
1+
---
2+
name: "Bug Report"
3+
about: "Report an issue to help the project improve."
4+
title: "[Bug] "
5+
labels: "Type: Bug"
6+
assignees: caffeine-addictt
7+
8+
---
9+
10+
# Bug report
11+
Your issue may already be reported!
12+
Please check out our [active issues](https://github.com/python-thread/thread-bot/issues) before creating one.
13+
14+
15+
16+
## Expected Behavior
17+
<!--
18+
If you're describing a bug, tell us what should happen
19+
If you're suggesting a change/improvement, tell us how it should work
20+
21+
Please include screenshots and/or code snippets if applicable
22+
-->
23+
24+
25+
26+
## Current Behavior
27+
<!--
28+
If describing a bug, tell us what happens instead of the expected behavior
29+
If suggesting a change/improvement, explain the difference from current behavior
30+
31+
Please include screenshots and/or code snippets if applicable
32+
-->
33+
34+
35+
36+
## Is this a regression?
37+
<!--
38+
Did this behaviour use to work in previous versions?
39+
If yes, what is the latest version where this behaviour is not present?
40+
-->
41+
42+
43+
44+
## Possible Solution
45+
<!--
46+
Not obligatory, but suggest a fix/reason for the bug
47+
or ideas how to implement the addition or change
48+
-->
49+
50+
51+
52+
## Steps to Reproduce (for bugs)
53+
<!--
54+
Provide a link to a live example, or an unambiguous set of steps to reproduce this bug.
55+
-->
56+
1.
57+
2.
58+
3.
59+
4.
60+
61+
62+
63+
## Context
64+
<!--
65+
How has this issue affected you?
66+
What are you trying to accomplish?
67+
68+
Providing context helps us come up with a solution that is most useful in the real world.
69+
70+
Please include screenshots and/or code snippets if applicable
71+
-->
72+
73+
74+
75+
## Your Environment
76+
<!--
77+
Include as many relevant details about the environment you experienced the bug in
78+
-->
79+
* Version used:
80+
* Python version:
81+
* Link to your project:
82+
* Operating System and version (desktop or mobile):

‎.github/ISSUE_TEMPLATE/2-feature-request.md

Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
---
2+
name: "Feature Request"
3+
about: "Suggest an idea or possible new feature for this project."
4+
title: ""
5+
labels: "Type: Feature"
6+
assignees: caffeine-addictt
7+
8+
---
9+
10+
# Feature Request
11+
Your issue may already be reported!
12+
Please check out our [active issues](https://github.com/python-thread/thread-bot/issues) before creating one.
13+
14+
15+
16+
## Is Your Feature Request Related to an Issue?
17+
<!--
18+
If yes, provide a clear and concise description of what the problem is
19+
E.g.:
20+
Issue #
21+
I'm always frustrated when...
22+
-->
23+
24+
25+
26+
## Describe the Solution You'd Like
27+
<!--
28+
A clear and concise description of what you'd like
29+
-->
30+
31+
32+
33+
## Describe Alternatives You've Considered
34+
<!--
35+
A clear and concise description of other alternatives you have considered
36+
-->
37+
38+
39+
40+
## Additional Context
41+
<!--
42+
Any other extra context or information
43+
-->

‎.github/ISSUE_TEMPLATE/3-seccurity-report.md

Lines changed: 97 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,97 @@
1+
---
2+
name: "Security Report"
3+
about: "Report an issue to help the project improve."
4+
title: ""
5+
labels: "Type: Security"
6+
assignees: caffeine-addictt
7+
8+
---
9+
10+
<!--
11+
12+
Oh, hi there! 😄
13+
14+
To expedite issue processing, please search open and closed issues before submitting a new one.
15+
Please read our Rules of Conduct at this repository's `.github/CODE_OF_CONDUCT.md`
16+
17+
FIRST OF ALL, read this project's SECURITY.md file. Located in `.github/SECURITY.md`.
18+
19+
READ CAREFULLY IF YOUR ISSUE REPORT CONTAINS SENSIBLE OR PRIVATE DATA:
20+
(data that might be leaked or subtracted from our servers due to this
21+
security issue).
22+
23+
If this security report (or the guide on how to "identify the security bug") includes
24+
certain personal information or involves personal identifiable data, or you believe
25+
that the data that you might leak by exposing the way on how to attack the project
26+
could be considered as a data leak or could violate the privacy of any kind of
27+
data or sensible data, please do not post it here and directly email the developer:
28+
(jgracia9988@gmail.com). You should post the issue with the least amount of
29+
sensible or private data as possible to help us manage the security issue, and
30+
with the extra data sent from your email to the developer (if any), we will deeply
31+
analyze and try to fix it as fast as possible.
32+
33+
If you are in doubt about the data that you might post here (screenshots or media
34+
also, count as data), please directly email us.
35+
36+
The data that must NOT be posted here:
37+
38+
* Legal and/or full names
39+
* Names or usernames combined with other identifiers like phone numbers or email addresses
40+
* Health or financial information (including insurance information, social security numbers, etc.)
41+
* Information about political or religious affiliations
42+
* Information about race, ethnicity, sexual orientation, gender, or other identifying information that could be used for discriminatory purposes
43+
44+
-->
45+
46+
# Security Report
47+
Your issue may already be reported!
48+
Please check out our [active issues](https://github.com/python-thread/thread-bot/issues) before creating one.
49+
50+
51+
52+
## Describe the Security Issue
53+
<!--
54+
A clear and concise description of the security issue
55+
-->
56+
57+
58+
59+
## Steps to Reproduce
60+
<!--
61+
e.g.:
62+
1. Navigate to x
63+
2. Go to...
64+
3. See error
65+
-->
66+
67+
68+
69+
## Expected Behavior
70+
<!--
71+
A clear and concise description of the expected behavior
72+
-->
73+
74+
75+
76+
## Media Prove
77+
<!--
78+
If applicable, provide screenshots, videos and/or code snippets
79+
-->
80+
81+
82+
83+
## Additional Context
84+
<!--
85+
Any other extra context or information
86+
-->
87+
88+
89+
90+
### Your Environment
91+
<!--
92+
Include as many relevant details about the environment you experienced the bug in
93+
-->
94+
* Version used:
95+
* Python version:
96+
* Link to your project:
97+
* Operating System and version (desktop or mobile):

‎.github/ISSUE_TEMPLATE/4-question-support.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: "Question or Support Request"
3+
about: "Questions and requests for support."
4+
title: ""
5+
labels: "Type: Question"
6+
assignees: caffeine-addictt
7+
8+
---
9+
10+
# Question or Support Request
11+
12+
13+
14+
15+
## Describe your question or ask for support
16+
<!--
17+
A clear and concise description of what your doubt is
18+
-->
19+
20+
*

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy