Merge pull request #2338 from unixfox/issue-template

add new issue template
This commit is contained in:
Alexandre Flament 2020-12-03 19:16:11 +01:00 committed by GitHub
commit f56e78ee80
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
4 changed files with 99 additions and 0 deletions

37
.github/ISSUE_TEMPLATE/bug-report.md vendored Normal file
View file

@ -0,0 +1,37 @@
---
name: Bug report
about: Report a bug in Searx
title: ''
labels: bug
assignees: ''
---
**Version of Searx, commit number if you are using on master branch and stipulate if you forked Searx**
<!-- If you are running on master branch using git execute this command
in order to fetch the latest commit ID:
```
git log -1
```
If you are using searx-docker then look at the bottom of the Searx page
and check for the version after "Powered by searx"
Please also stipulate if you are using a forked version of Searx and
include a link to the fork source code.
-->
**How did you install Searx?**
<!-- Did you install Searx using the official wiki or using searx-docker
or manually by executing the searx/webapp.py file? -->
**What happened?**
<!-- A clear and concise description of what the bug is. -->
**How To Reproduce**
<!-- How can we reproduce this issue? (as minimally and as precisely as possible) -->
**Expected behavior**
<!-- A clear and concise description of what you expected to happen. -->
**Screenshots & Logs**
<!-- If applicable, add screenshots, logs to help explain your problem. -->
**Additional context**
<!-- Add any other context about the problem here. -->

14
.github/ISSUE_TEMPLATE/config.yml vendored Normal file
View file

@ -0,0 +1,14 @@
blank_issues_enabled: true
contact_links:
- name: Installation issue using the official wiki
url: https://github.com/searx/searx/discussions/new?category_id=32001257
about: Ask for help if you are having some issue with installing Searx using the official wiki.
- name: Installation issue using searx-docker
url: https://github.com/searx/searx/discussions/new?category_id=32001259
about: Ask for help if you are having some issue with installing Searx using searx-docker.
- name: Installation issue without using the official wiki nor searx-docker
url: https://github.com/searx/searx/discussions/new?category_id=32001260
about: Ask for help if you are having some issue with installing Searx manually without using the wiki nor searx-docker.
- name: Report a bug on a public Searx instance
url: https://github.com/searx/searx/discussions/new?category_id=32001412
about: Report a bug that you discovered on a public Searx instance.

View file

@ -0,0 +1,29 @@
---
name: Engine request
about: Request a new engine in Searx
title: ''
labels: enhancement, engine request
assignees: ''
---
**Working URL to the engine**
<!-- Please check if the engine is responding correctly before submitting it. -->
**Why do you want to add this engine?**
<!-- What's special about this engine? Is it open source or libre? -->
**Features of this engine**
<!-- Features of this engine: Doesn't track its users, fast, easy to integrate, ... -->
**How can Searx fetch the information from this engine?**
<!-- List API URL, example code (using the correct markdown) and more
that could be useful for the developers in order to implement this engine.
If you don't know what to write, let this part blank.>
**Applicable category of this engine**
<!-- Where should this new engine fit in Searx? Current categories in Searx:
general, files, images, it, map, music, news, science, social media and videos.
You can add multiple categories at the same time. -->
**Additional context**
<!-- Add any other context about this engine here. -->

View file

@ -0,0 +1,19 @@
---
name: Feature request
about: Request a new feature in Searx
title: ''
labels: enhancement
assignees: ''
---
**Is your feature request related to a problem? Please describe.**
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
**Describe the solution you'd like**
<!-- A clear and concise description of what you want to happen. -->
**Describe alternatives you've considered**
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
**Additional context**
<!-- Add any other context or screenshots about the feature request here. -->