Merge pull request #8 from kyaulabs/release/1.2.4

Release/1.2.4

.github/CODEOWNERS

@@ -0,0 +1 @@
+*	@kyau

.github/FUNDING.yml

@@ -0,0 +1,2 @@
+github: kyau
+

.github/ISSUE_TEMPLATE/01_BUG_REPORT.md

@@ -0,0 +1,34 @@
+---
+name: "\U0001F41B Bug Report"
+about: "If something isn't working as expected \U0001F914."
+title: ''
+labels: 'i: bug, i: needs triage'
+assignees: ''
+
+---
+
+## Bug Report
+
+### Environment
+| Hardware        | Model                      |
+| ----------------| -------------------------- |
+| Platform        | *Desktop, Laptop, or Tablet* |
+| CPU             |                            |
+| GPU             |                            |
+| HDD             | *Disk, SSD, or NVME*       |
+| Windows Version | *Pro N*                    |
+| Windows Build   | *22621.169*                |
+
+### What is the expected behavior?
+
+### What is the actual behavior?
+
+### Additional information to reproduce the issue?
+
+Add any other content about the problem here. If applicable, add screenshots to help explain.
+
+### Possible Solution?
+
+### If the bug is confirmed, would you be willing to submit a PR?
+
+Yes / No *(Help can be provided if you need assistance submitting a PR)*

.github/ISSUE_TEMPLATE/02_FEATURE_REQUEST.md

@@ -0,0 +1,30 @@
+---
+name: "\U0001F680 Feature Request"
+about: "I have a suggestion (and may want to implement it \U0001F642)!"
+title: ''
+labels: 'i: enhancement, i: needs triage'
+assignees: ''
+
+---
+
+## Feature Request
+
+### What exactly are you trying to accomplish?
+
+*Context matters. What are you trying to do? Is this something you currently cannot do?*
+
+### Is your feature request related to an issue, problem or flaw?
+
+*Clear and concise description of what the problem is.*
+
+### Proposed Solution
+
+*Clear and concise description of what you want to happen. Add any considered drawbacks.*
+
+### Alternative Solutions
+
+*Clear and concise description of alternative solutions or methods you have considered. Is the alternative considerable?*
+
+### If the feature request is approved, would you be willing to submit a PR?
+
+Yes / No *(Help can be provided if you need assistance submitting a PR)*

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: ❓ Help and Support Discord Channel
+    url: https://discord.gg/DSvUNYm
+    about: Please ask and answer questions here. 📮

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,25 @@
+# Summary of the Pull Request
+
+# References
+
+# Gitleaks Output
+
+*Replace this text with the output of `gitleaks detect -v` wrapped in code block.*
+
+# PR Checklist
+
+## All Submissions:
+
+* [ ] Have you followed the guidelines in our Contributing document?
+* [ ] Have you checked to ensure there aren't other open [Pull Requests](../../../pulls) for the same update/change?
+* [ ] Does your submission ensure overall functionality?
+* [ ] Have you lint your code locally prior to submission?
+* [ ] Have you run your code through `zricethezav/gitleaks` prior to submission?
+
+## Changes to Core Features:
+
+* [ ] Have you added an explanation of what your changes do and why you would like us to include them?
+* [ ] Have you properly tested your changes?
+* [ ] Have you successfully ran through a local test installation with your changes?
+
+# Additional Comments

.github/workflows/psscriptanalyzer.yml

@@ -0,0 +1,19 @@
+name: CI
+
+on:
+  push:
+    branches: [ "master", "develop", "feature/**", "release/**" ]
+  pull_request:
+    branches: [ "master", "develop", "feature/**", "release/**" ]
+  workflow_dispatch:
+
+jobs:
+  build:
+    name: PSScriptAnalyzer
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v2
+    - name: Run PSScriptAnalyzer
+      uses: devblackops/github-action-psscriptanalyzer@master
+      with:
+        repoToken: ${{ secrets.GITHUB_TOKEN }}

.gitignore

@@ -0,0 +1,5 @@
+Resources/Icons/Apps
+Resources/Icons/Hardware
+Resources/Icons/Places
+Resources/Icons/Start
+Resources/Icons/convert.bat

CODE_OF_CONDUCT.md

@@ -0,0 +1,134 @@
+
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+git+abuse@kyaulabs.com.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations
+

CONTRIBUTING.md

@@ -0,0 +1,37 @@
+# Contributing
+
+Thanks for taking an interest in this project. We want to make contributing to this project as easy and transparent as possible, whether it is:
+
+* Reporting a bug
+* Discussing the current state of the code
+* Submitting a fix
+* Proposing new features
+* Becoming a maintainer
+
+## We Develop with Github
+
+We use Github to host code, to track issues and feature requests, as well as accept pull requests. Discussion and general support is typically done through Discord and/or Email.
+
+## We Use [Git Flow](https://www.gitkraken.com/learn/git/git-flow)
+
+All code changes happen through pull requests and are the best way to propose changes to the codebase. We actively welcome your pull requests:
+
+1. Fork the repo and create your own branch off of the `develop` branch.
+2. Name your branch `feature/<name>-<hash>-<desc>` where:
+  * `<name>` is your Github username
+  * `<hash>` is equal to `echo "$(openssl rand -hex 2)"`
+  * `<desc>` is a short description using hyphen as a separator
+3. If you have added code that should be tested, add tests.
+4. If you have changes APIs, update the documentation.
+5. Ensure it passes whatever tests are being used.
+6. Make sure your code lints.
+7. Issue the pull request!
+
+
+## Reporting Bugs / Feature Requests
+
+We use Github issues to track public bugs and feature requests. Report a bug/feature by [opening a new issue](/../../issues); it is that easy!
+
+## Contributions & Software Licensing
+
+In short, when you submit code changes, your submissions are understood to be under the same [license](LICENSE) that covers the project itself. If you have a concern about this, please refrain from submitting a PR and contact a maintainer directly.