README: recommend extension developers allow issues

README.md

@@ -15,5 +15,6 @@ This is intended to showcase:
 Forking the repository will try to automatically package and upload your Extension variant to a Docker registry (Docker Hub), using the built in GitHub Action.
 This process makes use of some [GitHub Variables](https://github.com/BlueOS-community/Deploy-BlueOS-Extension#input-variables) that you can configure for your fork.
 
-It is also possible to manually run the Action (via the Actions tab), or to build and deploy the extension manually on your local machine (although this requires
-installing the relevant build tools and cloning the repository onto your computer).
+It is also possible to manually run the Action (via the Actions tab), or to build and deploy the extension manually on your local machine (although this requires installing the relevant build tools and cloning the repository onto your computer).
+
+>💡**Note:** If you are forking this repository as a starting point for creating your own [BlueOS Extension](https://blueos.cloud/docs/blueos/latest/development/extensions), it is recommended to enable `Issues` in your fork (via the `Settings` tab at the top), so that users and co-developers of your Extension can raise problems and make suggestions.