Add references to Troubleshoting discussion page

Ulauncher · Mar 18, 2022 · 6568416 · 6568416
1 parent 31576d4
commit 6568416
Show file tree

Hide file tree

Showing 3 changed files with 6 additions and 11 deletions.
diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml
@@ -30,9 +30,9 @@ body:
     id: communication-guidelines
     attributes:
       label: Communication guidelines
-      description: Did you read the [communication guidelines](https://github.com/Ulauncher/Ulauncher/blob/dev/CODE_OF_CONDUCT.md#general-communication-guidelines)?
+      description: Did you read the [communication guidelines](https://github.com/Ulauncher/Ulauncher/blob/dev/CODE_OF_CONDUCT.md#general-communication-guidelines) and [troubleshooting page](https://github.com/Ulauncher/Ulauncher/discussions/991)?
       options:
-        - label: I have read and agree with Ulauncher's communication guidelines.
+        - label: I have read and agree with Ulauncher's communication guidelines and checked the troubleshooting page for self-help.
           required: true
   - type: checkboxes
     id: no-extension

diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
@@ -18,7 +18,7 @@ We will not tolerate harassment, personal attacks, derogatory comments, trolling
 
 The maintainers and contributors want their time spent contributing to Ulauncher to be as productive and constructive as possible. Please respect this time when you are requesting help, improvements, or new features. Do your due diligence before you report issues or contact us asking for help. Read the actual error messages you are getting (if any), and don't ask us about things that are documented or previously covered. We have to prioritize tasks based on how helpful the reports were, and close issues that don't provide enough information.
 
-1. Our [Readme](https://github.com/Ulauncher/Ulauncher#readme), [Issue tracker](https://github.com/Ulauncher/Ulauncher/issues) and [Dicussions](https://github.com/Ulauncher/Ulauncher/discussions) have many answers, and you should search for these before you ask for help. You can use the GitHub search box (located to the upper left on a desktop computer) to search all of these. Often you can find help or similar issues there rather than starting a new issue. If you can't find any information or references to your issue in our repository, then it's likely that the error is not directly with the Ulauncher code, but an issue with your system, or Ulauncher's dependencies on your system, but it may be good to create an issue or discussion anyway in case others have the same issue.
+1. Our [Dicussions](https://github.com/Ulauncher/Ulauncher/discussions) and [Issue tracker](https://github.com/Ulauncher/Ulauncher/issues) have many answers, in particular the [Troubleshooting](https://github.com/Ulauncher/Ulauncher/discussions/991) discussion paage. Please use these before you ask for help. You can use the GitHub search box (located to the upper left on a desktop computer) to search all of these. Often you can find help or similar issues there rather than starting a new issue. If you can't find any information or references to your issue in our repository, then it's likely that the error is not directly with the Ulauncher code, but an issue with your system, or Ulauncher's dependencies on your system, but it may be good to create an issue or discussion anyway in case others have the same issue.
 2. Our [Developer resources](https://github.com/Ulauncher/Ulauncher/discussions/879) have more help to offer for extension developers, color theme developers and contributors.
 3. If you find an issue and want to show that you agree with a previous comment, use the :+1: reaction. Do not write a comment if you want to repeat something that has already been said or want to know when something will be implemented.
 4. Please understand that there are lots of standards, environments, priorities, use-cases, dependencies and architectural debts/costs that makes software development hard and time-consuming. Ulauncher makes no money and and all of our volunteers are limited to their spare time. You cannot expect or demand our time to address your specific concerns. Only those actually volunteering their time to help out have an influence on priority, what gets implemented, how it gets implemented and the direction of the project.

diff --git a/README.md b/README.md
@@ -26,14 +26,9 @@ systemctl --user enable --now ulauncher
 If not, then you can open Ulauncher and enable "Launch at Login" in the preferences.
 
 
-### Known Issues and workarounds
-
-* If your DE doesn't use compositing, run ulauncher with `--no-window-shadow` to remove a black box around a window
-* [inotify watch limit reached](https://github.com/Ulauncher/Ulauncher/issues/51)
-* [Can't map the keys to ALT+SPACE](https://github.com/Ulauncher/Ulauncher/issues/100)
-* [Hotkey doesn't work in Wayland when is triggered from certain apps](https://github.com/Ulauncher/Ulauncher/issues/183)
-* [Border appears around ulauncher window in Sway DE](https://github.com/Ulauncher/Ulauncher/issues/230#issuecomment-570736422)
-* [Pass custom environment variable to Ulauncher](https://github.com/Ulauncher/Ulauncher/issues/780#issuecomment-912982174)
+### Troubleshooting
+
+Please read our discussion page [Troubleshooting - Quirks and workaround](https://github.com/Ulauncher/Ulauncher/discussions/991) if you run into issues, and also check our outher discussions and issues if you still need help after this.
 
 
 ### Code Contributions