[TASK] Rework how we solicate feedback (#1501)

We have decided to no longer ask users to create GitHub issues for
feedback as this doesn't work well with how we work.

- drop the issue template for technical feedback
- in the README, link to GitHub discussions instead of issues

Fixes #1500

.github/ISSUE_TEMPLATE/technical_feedback.md

@@ -1,14 +0,0 @@
----
-name: Technical Feedback
-about: Provide technical feedback to help us improve
-title: "Technical Feedback: Please add a speaking title"
-labels: 'feedback'
-assignees: ''
-
----
-
-**Describe the area**
-A short introduction to the area, e.g. a decision regarding file formats, location, etc.
-
-**Feedback**
-Your feedback, e.g. what would you do instead, what are pros and cons of the different ways in doing things.

.github/dependabot.yml

@@ -9,7 +9,7 @@ updates:
     # adjust this number according to your own milestones if used.
     milestone: 12
     commit-message:
-      prefix: "[TASK] "
+      prefix: "[TASK][Dependabot] "
 
   - package-ecosystem: "composer"
     directory: "/"
@@ -30,7 +30,7 @@ updates:
     # adjust this number according to your own milestones if used.
     milestone: 12
     commit-message:
-      prefix: "[TASK] "
+      prefix: "[TASK][Dependabot] "
 
   - package-ecosystem: "npm"
     directory: "/"
@@ -40,4 +40,4 @@ updates:
     # adjust this number according to your own milestones if used.
     milestone: 12
     commit-message:
-      prefix: "[TASK] "
+      prefix: "[TASK][Dependabot] "

README.md

@@ -26,7 +26,7 @@ You can also use this extension to manage your collection of delicious teas.
 We value and welcome feedback of all kinds, including discussions.
 Feedback can be sent via TYPO3 slack within [our channel](https://app.slack.com/client/T024TUMLZ/CSQ8T0VS5) or via direct massages to the team members.
 We also welcome email. All the contact information is available at our [typo3.org team page](https://typo3.org/community/teams/best-practices).
-Another way is to open an [issue on GitHub](https://github.com/FriendsOfTYPO3/tea/issues/new/choose).
+Another way is to create a [discussion on GitHub](https://github.com/FriendsOfTYPO3/tea/discussions).
 
 ## Philosophies
 

Tests/Unit/Controller/FrontEndEditorControllerTest.php

@@ -22,6 +22,9 @@ use TYPO3\TestingFramework\Core\AccessibleObjectInterface;
 use TYPO3\TestingFramework\Core\Unit\UnitTestCase;
 
 /**
+ * Note: Unit tests for controllers are not considered best practice anymore. Instead, functional tests should be used.
+ * We're currently in the process of migrating all controller tests to functional tests.
+ *
  * @covers \TTN\Tea\Controller\FrontEndEditorController
  */
 final class FrontEndEditorControllerTest extends UnitTestCase

Tests/Unit/Controller/TeaControllerTest.php

@@ -17,6 +17,9 @@ use TYPO3\TestingFramework\Core\AccessibleObjectInterface;
 use TYPO3\TestingFramework\Core\Unit\UnitTestCase;
 
 /**
+ * Note: Unit tests for controllers are not considered best practice anymore. Instead, functional tests should be used.
+ * We're currently in the process of migrating all controller tests to functional tests.
+ *
  * @covers \TTN\Tea\Controller\TeaController
  */
 final class TeaControllerTest extends UnitTestCase