[98] update github files

.github/ISSUE_TEMPLATE/1.bug_report.yml

@@ -0,0 +1,54 @@
+name: Bug Report
+description: Please do not use bug reports for support issues.
+title: '[Bug]: '
+labels: ['status:not-yet-viewed', 'bug']
+assignees: 'meisnate12'
+
+body:
+  - type: markdown
+    attributes:
+      value: >
+        **THIS IS NOT THE PLACE TO ASK FOR SUPPORT!**
+        Please use [Ple Meta Manager Discord](https://discord.gg/NfH6mGFuAB) and post your question under the `plex-meta-manager` channel for support issues.
+  - type: input
+    id: version
+    attributes:
+      label: Version Number
+      description: Can be found at the beginning of your log file
+      placeholder: eg. 1.16.0
+    validations:
+      required: true
+  - type: dropdown
+    id: branch
+    attributes:
+      label: What branch are you on?
+      options:
+        - master
+        - develop
+        - nightly
+    validations:
+      required: true
+  - type: textarea
+    id: description
+    attributes:
+      label: Describe the Bug
+      description: A clear and concise description of the bug.
+    validations:
+      required: true
+  - type: textarea
+    id: config
+    attributes:
+      label: Relevant Collection/Playlist Definition
+      description: >
+        If you issue is happening with a specific collection/playlist please paste your definition here
+        This will be automatically formatted into code, so no need for backticks.
+      render: yml
+  - type: input
+    id: logs
+    attributes:
+      label: Logs
+      description: >
+        Please share the relevant log file with the error on [Gist](https://gist.github.com).
+      placeholder: "https://gist.github.com"
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/2.feature_request.yml

@@ -0,0 +1,31 @@
+name: Feature Request
+description: Suggest a new feature for Plex Meta Manager.
+title: '[Feature]: '
+labels: ['status:not-yet-viewed', 'enhancement']
+assignees: 'meisnate12'
+
+body:
+  - type: markdown
+    attributes:
+      value: >
+        Thanks for taking the time to file a feature request! Please fill out this form as completely as possible.
+  - type: textarea
+    id: problem-relation
+    attributes:
+      label: Is your feature request related to a problem? Please elaborate.
+      description: A clear and concise description of what the problem is.
+      placeholder: eg. I'm always frustrated when...
+    validations:
+      required: true
+  - type: textarea
+    id: solution
+    attributes:
+      label: Describe the solution you'd like
+      description: A clear and concise description of what you want to happen.
+    validations:
+      required: true
+  - type: textarea
+    id: additional-info
+    attributes:
+      label: Additional Information
+      description: "[optional] You may provide additional context or screenshots for us to better understand the need of the feature."

.github/ISSUE_TEMPLATE/3.docs_request.yml

@@ -0,0 +1,18 @@
+name: Documentation Request
+description: A request to update or improve Plex Meta Manager's documentation
+title: '[Docs]: '
+labels: ['status:not-yet-viewed', 'documentation']
+assignees: 'meisnate12'
+
+body:
+  - type: textarea
+    attributes:
+      label: What is the improvement or update to the Documentation you wish to see?
+    validations:
+      required: true
+  - type: input
+    attributes:
+      label: Does the docs page already exist? Please link to it.
+      description: 'Example: https://metamanager.wiki/en/latest/config/operations.html'
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,25 +0,0 @@
----
-name: Bug Report
-about: Please do not use bug reports for support issues.
-title: 'Bug: '
-labels: 'status:not-yet-viewed, bug'
-assignees: 'meisnate12'
-
----
-
-<!---
-THIS IS NOT THE PLACE TO ASK FOR SUPPORT! Please use [Discord](https://discord.gg/TsdpsFYqqm) for support issues.
-DO NOT ERASE THE TEMPLATE! Please complete the entire template.
---->
-
-**Describe the Bug**
-A clear and concise description of what the bug is.
-
-**Relevant Collection Config**
-- Having a problem with a collection include the collection config from your metadata file.
-
-**Plex Meta Manager Info**
-- Version Number (can be found at the beginning of your meta.log file.
-
-**Link to logs (required)**
-- If having an error with a specific collection include the collection.log otherwise please include the full meta.log file on [Gist](http://gist.github.com). _Do not upload attachments_.

.github/ISSUE_TEMPLATE/config.yml

@@ -1,8 +1,8 @@
 blank_issues_enabled: false
 contact_links:
   - name: Plex Meta Manager Wiki
-    url: https://github.com/meisnate12/Plex-Meta-Manager/wiki
+    url: https://metamanager.wiki
     about: Please check the wiki to see if your question has already been answered.
   - name: Discord
-    url: https://discord.gg/TsdpsFYqqm
+    url: https://discord.gg/NfH6mGFuAB
-    about: Please use Discord to ask for support.
+    about: Please use the Plex Meta Manager Discord to ask for support.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,24 +0,0 @@
----
-name: Feature Request
-about: Suggest a new feature for Plex Meta Manager.
-title: 'Feature Request: '
-labels: 'status:not-yet-viewed, enhancement'
-assignees: 'meisnate12'
-
----
-
-<!---
-Please make sure you submit all Pull Requests to the develop branch not the master branch.
---->
-
-**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.

.github/dependabot.yml

@@ -10,3 +10,13 @@ updates:
     schedule:
       interval: "daily"
     target-branch: "develop"
+    assignees:
+      - "meisnate12"
+  - package-ecosystem: github-actions
+    directory: '/'
+    schedule:
+      interval: daily
+    assignees:
+      - "meisnate12"
+    ignore:
+      - dependency-name: "salsify/action-detect-and-tag-new-version"

.github/workflows/develop.yml

@@ -14,7 +14,7 @@ jobs:
     steps:
 
       - name: Check Out Repo
-        uses: actions/checkout@v2
+        uses: actions/checkout@v3
         with:
           ref: develop
 

.github/workflows/latest.yml

@@ -12,7 +12,7 @@ jobs:
     steps:
 
       - name: Check Out Repo
-        uses: actions/checkout@v2
+        uses: actions/checkout@v3
 
       - name: Login to Docker Hub
         uses: docker/login-action@v1

.github/workflows/nightly.yml

@@ -14,7 +14,7 @@ jobs:
     steps:
 
       - name: Check Out Repo
-        uses: actions/checkout@v2
+        uses: actions/checkout@v3
         with:
           ref: nightly
 

.github/workflows/tag.yml

@@ -8,7 +8,7 @@ jobs:
   tag-new-versions:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v3
         with:
           token: ${{ secrets.PAT }}
           fetch-depth: 2

.github/workflows/version.yml

@@ -13,7 +13,7 @@ jobs:
     steps:
 
       - name: Check Out Repo
-        uses: actions/checkout@v2
+        uses: actions/checkout@v3
 
       - name: Login to Docker Hub
         uses: docker/login-action@v1

VERSION

@@ -1 +1 @@
-1.15.1-develop97
+1.15.1-develop98