git.iko.soy/searx
on master help sign in
add new issue template
741c31fEmilien Devos
.github/ISSUE_TEMPLATE/bug-report.mdnew file+37
compare with master
unifiedsplit
@@ -0,0 +1,37 @@
1+---
2+name: Bug report
3+about: Report a bug in Searx
4+title: ''
5+labels: bug
6+assignees: ''
7+
8+---
9+**Version of Searx, commit number if you are using on master branch and stipulate if you forked Searx**
10+<!-- If you are running on master branch using git execute this command
11+in order to fetch the latest commit ID:
12+```
13+git log -1
14+```
15+If you are using searx-docker then look at the bottom of the Searx page
16+and check for the version after "Powered by searx"
17+
18+Please also stipulate if you are using a forked version of Searx and
19+include a link to the fork source code.
20+-->
21+**How did you install Searx?**
22+<!-- Did you install Searx using the official wiki or using searx-docker
23+or manually by executing the searx/webapp.py file? -->
24+**What happened?**
25+<!-- A clear and concise description of what the bug is. -->
26+
27+**How To Reproduce**
28+<!-- How can we reproduce this issue? (as minimally and as precisely as possible) -->
29+
30+**Expected behavior**
31+<!-- A clear and concise description of what you expected to happen. -->
32+
33+**Screenshots & Logs**
34+<!-- If applicable, add screenshots, logs to help explain your problem. -->
35+
36+**Additional context**
37+<!-- Add any other context about the problem here. -->
.github/ISSUE_TEMPLATE/config.ymlnew file+14
@@ -0,0 +1,14 @@
1+blank_issues_enabled: true
2+contact_links:
3+ - name: Installation issue using the official wiki
4+ url: https://github.com/searx/searx/discussions/new?category_id=32001257
5+ about: Ask for help if you are having some issue with installing Searx using the official wiki.
6+ - name: Installation issue using searx-docker
7+ url: https://github.com/searx/searx/discussions/new?category_id=32001259
8+ about: Ask for help if you are having some issue with installing Searx using searx-docker.
9+ - name: Installation issue without using the official wiki nor searx-docker
10+ url: https://github.com/searx/searx/discussions/new?category_id=32001260
11+ about: Ask for help if you are having some issue with installing Searx manually without using the wiki nor searx-docker.
12+ - name: Report a bug on a public Searx instance
13+ url: https://github.com/searx/searx/discussions/new?category_id=32001412
14+ about: Report a bug that you discovered on a public Searx instance.
.github/ISSUE_TEMPLATE/engine-request.mdnew file+29
@@ -0,0 +1,29 @@
1+---
2+name: Engine request
3+about: Request a new engine in Searx
4+title: ''
5+labels: enhancement, engine request
6+assignees: ''
7+
8+---
9+**Working URL to the engine**
10+<!-- Please check if the engine is responding correctly before submitting it. -->
11+
12+**Why do you want to add this engine?**
13+<!-- What's special about this engine? Is it open source or libre? -->
14+
15+**Features of this engine**
16+<!-- Features of this engine: Doesn't track its users, fast, easy to integrate, ... -->
17+
18+**How can Searx fetch the information from this engine?**
19+<!-- List API URL, example code (using the correct markdown) and more
20+that could be useful for the developers in order to implement this engine.
21+If you don't know what to write, let this part blank.>
22+
23+**Applicable category of this engine**
24+<!-- Where should this new engine fit in Searx? Current categories in Searx:
25+general, files, images, it, map, music, news, science, social media and videos.
26+You can add multiple categories at the same time. -->
27+
28+**Additional context**
29+<!-- Add any other context about this engine here. -->
.github/ISSUE_TEMPLATE/feature-request.mdnew file+19
@@ -0,0 +1,19 @@
1+---
2+name: Feature request
3+about: Request a new feature in Searx
4+title: ''
5+labels: enhancement
6+assignees: ''
7+
8+---
9+**Is your feature request related to a problem? Please describe.**
10+<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
11+
12+**Describe the solution you'd like**
13+<!-- A clear and concise description of what you want to happen. -->
14+
15+**Describe alternatives you've considered**
16+<!-- A clear and concise description of any alternative solutions or features you've considered. -->
17+
18+**Additional context**
19+<!-- Add any other context or screenshots about the feature request here. -->