WIP: Maintain and update repo

.github/ISSUE_TEMPLATE/.github/ISSUE_TEMPLATE/FIRST_TIMERS_ISSUE_TEMPLATE.md

@@ -0,0 +1,33 @@
+<!-- @format -->
+
+<!-- this issue template is used by https://github.com/apps/first-timers -->
+
+### 🆕🐥☝ First Timers Only
+
+This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝
+
+[About First Timers Only](http://www.firsttimersonly.com/).
+
+### 🤔 What you will need to know
+
+Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you trough the process.
+
+### :clipboard: Step by Step
+
+- [ ] 🙋 **Claim this issue**: Comment below
+      Please 🙏 only claim if you want to start working on it within a day. We will select a person at random as the contributor the day after the issue is created.
+      Once claimed we add you as contributor to this repository.
+- [ ] 👌 **Accept our invitation** to this repository. Once accepted, assign yourself to this repository
+- [ ] 🔄 **replace** the `DevOps` (Developer) Project with `ComOps` (Community).
+- [ ] 📝 **Update** the file [\$FILENAME in the `$REPO` repository]($BRANCH_URL) (press the little pen Icon) and edit the line as shown below.
+
+```diff
+$DIFF
+```
+
+- [ ] 🔀 **Start a Pull Request**. Mention `closes #THIS_ISSUE_NUMBER` in the description. There are two ways how you can start a pull request:
+  1. If you are familiar with the terminal or would like to learn it, [here is a great tutorial](https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github) on how to send a pull request using the terminal.
+  2. You can [edit files directly in your browser](https://help.github.com/articles/editing-files-in-your-repository/)
+- [ ] 🏁 **Done** :+1: Move your task in the projects to `Awaiting Review` column. Ask in comments for a review :)
+
+<!-- ### 🤔❓ Questions -->

.github/ISSUE_TEMPLATE/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,72 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: "bug([context]): "
+---
+
+<!-- @format -->
+
+<!-- Please use [context] in title to describe the package related to this issue.
+Valid options are; Release, Label, Variable, Installer
+context example: bug(installer): {your title here}
+-->
+
+## Describe the bug
+
+<!-- A clear and concise description of what the bug is. -->
+
+### To Reproduce
+
+<!-- Steps to reproduce the behaviour:-->
+
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+### Expected behaviour
+
+<!-- A clear and concise description of what you expected to happen. -->
+
+### Screenshots
+
+### Console Logs
+
+<!-- Please [set the `ACTIONS_RUNNER_DEBUG` secret to `true` to enable debug logging](https://help.github.com/en/actions/configuring-and-managing-workflows/managing-a-workflow-run#enabling-debug-logging), rerun the labeler workflow, and paste the output below: -->
+
+```
+insert debug output here
+```
+
+## Device Information
+
+<!-- Please delete all information not relivent-->
+
+- Version: [e.g. 22]
+- Platform: [e.g. macOS, Google Cloud, ubuntu 18.04]
+- Browser: [e.g. stock browser, safari]
+- Node Version: [e.g. v16.8.0]
+- Yarn Version: [e.g. v1.22.4]
+- Docker Version: [e.g. Docker version 19.03.12, build 48a66213fe]
+- Package(s): [e.g. @videndum/release-manager]
+- URL: [e.g. https://console.smartcloud.gg/admin]
+
+## Additional context
+
+<!-- Add any other context about the problem here. -->
+
+## Bug Checklist
+
+<!-- Please be honest here; we don't mind if you haven't done all these steps; however, we need to know where has been tested and how extensively we need to test it ourselves.
+
+We would appreciate it if you could maintain this section cleanly and clearly. If someone confirms your bug, add them to the "Bug confirmed by" section. Our bot will automatically detect if you have enough users confirmed to tag this bug as "Bug - Confirmed".
+-->
+
+- [ ] Have reproduced on my application version
+- [ ] Have reproduced on a clean installation
+- [ ] Have reproduced on a development build
+- [ ] Have included logs or screenshots
+- [ ] Have contacted support via the official website
+- [ ] Have asked the community for guidance
+- [ ] Have linked any related issues
+- [ ] Bug confirmed by <!--@yourusername & @friendsusername-->

.github/ISSUE_TEMPLATE/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,19 @@
+# @format
+
+blank_issues_enabled: false
+contact_links:
+  - name: Discussion
+    url: https://github.com/Videndum/action-masterminds/discussions/new
+    about: Start a converstation about our project
+  - name: Question & Answers
+    url: https://github.com/Videndum/action-masterminds/discussions/new
+    about: Start a converstation about our project
+  - name: Feature Requests
+    url: https://github.com/Videndum/action-masterminds/discussions/new
+    about: Open a feature request discussion
+  - name: Project Showcase
+    url: https://github.com/Videndum/action-masterminds/discussions/new
+    about: Showcase your project using our project
+  - name: Join the discord community
+    url: https://videndum.studio/discord
+    about: Looking for help with our projects, this is an amazing place to start

.github/ISSUE_TEMPLATE/.github/ISSUE_TEMPLATE/doc_review.md

@@ -0,0 +1,39 @@
+---
+name: Documentation review
+about: A review to highlight issues in documentation
+title: "docs([context]): "
+---
+
+<!-- @format -->
+
+<!-- Please use [context] in title to describe the package related to this issue.
+Valid options are; Release, Label, Variable, Installer
+context example: bug(installer): {your title here}
+-->
+
+## Problem to solve
+
+<!-- Please delete all information not relivent-->
+
+- What product or feature(s) affected?
+- What docs or doc section involved? Include links or paths.
+- Is there a problem with a specific document, or a feature/process that's not addressed sufficiently in docs?
+- Any other ideas or requests?
+- Any concepts, procedures, reference info we could add to make it easier to use our project successfully?
+- Include use cases, benefits, and/or goals for this work.
+- If adding content: What audience is it intended? (What roles and scenarios?)
+
+<!-- Uncomment if you have specifics for how can we solve the problem. You should include guidance to who can address the issue, normally by seeing who last updated the file or functionality which caused the documentation to get outdated.
+## Proposal
+-->
+
+## References
+
+<!-- Please delete all information not relivent-->
+
+Related Pull Request(s):
+Related issue(s):
+
+<!-- Uncomment for any additional context, questions, or notes for the technical writer.
+## Further Details
+-->

.github/ISSUE_TEMPLATE/.github/ISSUE_TEMPLATE/fix.md

@@ -0,0 +1,57 @@
+---
+name: Code fix
+about: Let us know about a solution to an existing bug
+title: "fix([context]): "
+---
+
+<!-- @format -->
+
+<!-- Please use [context] in title to describe the package related to this issue.
+Valid options are; Release, Label, Variable, Installer
+context example: bug(installer): {your title here}
+-->
+
+## Describe the fix
+
+Addresses bug: #{number}
+
+<!-- A clear and concise description of what the fix is. -->
+
+### Expected behaviour
+
+<!-- A clear and concise description of what you expected to happen. -->
+
+### Screenshots
+
+### Console Logs
+
+## Device Information
+
+<!-- Please delete all information not relivent-->
+
+- Version: [e.g. 22]
+- Platform: [e.g. macOS, Google Cloud, ubuntu 18.04]
+- Browser: [e.g. stock browser, safari]
+- Node Version: [e.g. v16.8.0]
+- Yarn Version: [e.g. v1.22.4]
+- Docker Version: [e.g. Docker version 19.03.12, build 48a66213fe]
+- Package(s): [e.g. @videndum/release-mastermind]
+- URL: [e.g. https://console.smartcloud.gg/admin]
+
+## Additional context
+
+<!-- Add any other context about the problem here. -->
+
+## Fix Checklist
+
+<!-- Please be honest here; we don't mind if you haven't done all these steps; however, we need to know where has been tested and how extensively we need to test it ourselves.
+
+We would appreciate it if you could maintain this section cleanly and clearly. If someone confirms your bug, add them to the "Fix confirmed by" section. Our bot will automatically detect if you have enough users confirmed to tag this bug as "Fix - Confirmed".
+-->
+
+- [ ] Have fixed on a clean installation
+- [ ] Have fixed on a stable build
+- [ ] Have fixed on a development build
+- [ ] Have included logs or screenshots
+- [ ] Have linked any related issues
+- [ ] Fix confirmed by <!--@yourusername & @friendsusername-->

.github/ISSUE_TEMPLATE/.github/ISSUE_TEMPLATE/maintenance.md

@@ -0,0 +1,46 @@
+---
+name: Code maintenance
+about: Requesting Styling, Refactoring, Optimisation, Revert, Deprecated or Removal of an existing feature
+title: "maintenance([context]): "
+---
+
+<!-- @format -->
+
+<!-- Please use [context] in title to describe the package related to this issue.
+Valid options are; Release, Label, Variable, Installer
+context example: bug(installer): {your title here}
+-->
+
+## Maintenance Required
+
+Type: <!-- Style, Refactoring, Optimisation, Revert, Deprecated, Removal -->
+Assignee: <!-- Who would you suggest does this? We suggest using blame to see who was the last to update the section. If unsure leave blank -->
+Risk: <!-- The risk associated with this change based on reliance of other features: Low, Medium, High -->
+
+<!-- Discribe maintenance is required -->
+
+<!-- Please include the code section which needs maintenance if under 50 lines -->
+
+https://github.com/Videndum/Smartcloud/blob/5fbd201d7edfc6f32b34105a15729384bfcae134/package.json#L12-L16
+
+## Improvements
+
+<!-- Explain the benefits of this maintenance.
+
+Transparent changes have the reasons for the change laid out clearly along with the change itself. This leads to fewer questions later on because people already have some understanding. A change with no public explanation can lead to a lot of extra rounds of questioning, which is less efficient. Avoid using terms such as "industry standard" or "best practices" as they are vague, opaque, and don't provide enough context as a reason for a change. -->
+
+## Expected risks
+
+<!-- Please list features that can break because of this maintenance and how you intend to solve that. -->
+
+## Involved components
+
+<!-- List files or directories that will be changed by the maintenance. -->
+
+<!-- Uncomment to add screenshots to help explain your problem.
+## Screenshots
+-->
+
+<!-- Uncomment to add any other context.
+## Additional context
+-->

.github/ISSUE_TEMPLATE/.github/ISSUE_TEMPLATE/outdated/discussion.md

@@ -0,0 +1,18 @@
+---
+name: Open discussion
+about: Openly discussing this project
+title: "discussion([context]): "
+---
+
+<!-- @format -->
+
+<!-- Please use [context] in title to describe the package related to this issue.
+Valid options are; Release, Label, Variable, Installer
+context example: bug(installer): {your title here}
+-->
+
+## Discussion initialiser
+
+<!-- A shortened and brief introduction to what you want to discuss -->
+
+I want to discuss the possibility of ...

.github/ISSUE_TEMPLATE/.github/ISSUE_TEMPLATE/outdated/feature_request.md

@@ -0,0 +1,62 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: "feat([context]): "
+---
+
+<!-- @format -->
+
+<!-- Please use [context] in title to describe the package related to this issue.
+Valid options are; Release, Label, Variable, Installer
+context example: bug(installer): {your title here}
+-->
+
+### My feature request explained
+
+<!-- A clear and concise description of what the problem is. E.g. I'm always frustrated when [...]
+
+Include:
+- use cases
+- benefits
+- goals
+- does it contribute to our vision?
+-->
+
+### Describe the solution you'd like
+
+<!-- A clear and concise description of what you want to happen. -->
+
+### Intended users
+
+<!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later. -->
+
+### Describe alternatives you've considered
+
+<!-- A clear and concise description of any alternative solutions or features you've considered. -->
+
+### Permissions and Security
+
+<!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users and groups as appropriate? Is the proposed behaviour consistent between the UI, API, and other access methods (e.g. email replies)? -->
+
+### Device Information
+
+<!-- Please tell us what devices should be able to do the feature. Please note that some devices may have differing capabilities depending on OS version. -->
+
+<!-- Please delete all information not relivent-->
+
+- Version: [e.g. 22]
+- Platform: [e.g. macOS, Google Cloud, ubuntu 18.04]
+- Browser: [e.g. stock browser, safari]
+- Node Version: [e.g. v16.8.0]
+- Yarn Version: [e.g. v1.22.4]
+- Docker Version: [e.g. Docker version 19.03.12, build 48a66213fe]
+- Package(s): [e.g. @videndum/release-mastermind]
+- URL: [e.g. https://console.smartcloud.gg/admin]
+
+### What does success look like, and how can we measure
+
+<!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. -->
+
+<!-- Uncomment to add any other context or screenshots about the feature request here.
+### Additional context
+-->

.github/ISSUE_TEMPLATE/.github/ISSUE_TEMPLATE/unknown.md

@@ -0,0 +1,36 @@
+---
+name: Unknown issue type
+about: For use when other issue templates don't work for your issue
+title: "<type>([context]): "
+---
+
+<!-- @format -->
+
+<!--
+Please use <type> in title to describe the type of issue you are raising. Note that we use semantic titles in our pull requests, so where possible please stick to that format.
+
+Please use [context] in title to describe the package related to this issue.
+Valid options are; Release, Label, Variable, Installer
+context example: bug(installer): {your title here}
+-->
+
+## Issue details
+
+<!--Literally whatever you think you need. You chose this template because all other templates didn't fit... -->
+
+<!-- Uncomment if you want to request a new issue template
+We want to make it easy for everyone to use our github, and sometime we don't have a template which works right. Here we would like you to ask you what template needs adding?
+
+## Issue Template Request
+-->
+
+<!-- [META]
+name:
+about:
+title:
+labels:
+assigned:
+-->
+
+<!-- [BODY] -->
+<!-- Here goes whatever you think the body should be. You can include comments in this section-->