Add first interaction greeting and auto close prs automations

.github/workflows/close-prs.yml

@@ -0,0 +1,14 @@
+name: Close Pull Request
+
+on:
+  pull_request_target:
+    types: [opened, reopened]
+
+jobs:
+  run:
+    if: github.actor != 'dependabot[bot]'
+    runs-on: ubuntu-latest
+    steps:
+    - uses: superbrothers/close-pull-request@v3
+      with:
+        comment: "We do not accept PRs. If you'd like to propose a change, please contact us at our Telegram supergroup."

.github/workflows/greeting.yml

@@ -0,0 +1,34 @@
+name: First Interaction Greeting
+
+on: [issues]
+
+jobs:
+  greeting:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/first-interaction@v1
+      with:
+        repo-token: ${{ github.token }}
+        issue-message: |
+          Greetings. It seems like this is the first issue you open on this repository.
+
+          We are letting you know that these are for bug reports or feature requests. Most of the reports we receive in this GitHub Organisation are user errors.
+          
+          For the sake of saving time, here are the most common cases:
+          - Outdated version of this kext.
+          - Conflicts with other kexts (e.g. `WhateverGreen`, `NootedRed`).
+          - Issues caused by other kexts like memory corruption (e.g. `AirportItlwm`).
+          - Intended behaviour by Apple (e.g. V-Sync or cursor rendering).
+          - Using cheap hacks like kext/library downgrades (e.g. `OCLP`, `BFixup`).
+          - Duplicate kexts.
+          - Malformed `config.plist` caused by configurator software (`OCAT`, `OCC`, etc).
+          - Outdated macOS minor version (e.g. macOS 11.0.0 instead of latest).
+          - Using beta versions of macOS.
+          - Using the kext during installation or update. There is a Lilu bug which makes macOS stall during the last install phase.
+          - Incorrect SMBIOS.
+
+          We will never support the use of configurator software, solutions like OCLP/BFixup, or using macOS beta versions.
+
+          This issue will be looked over by the respective maintainer when they can. In the meantime, look if you can resolve this yourself via checking the above. 
+          
+          Be patient, we are hobbyists.