initialize repo

.gitattributes

@@ -0,0 +1,15 @@
+# Needed for publishing of examples, build worker defaults to core.autocrlf=input.
+* text eol=autocrlf
+
+*.mof   text eol=crlf
+*.sh    text eol=lf
+*.svg   eol=lf
+
+# Ensure any exe files are treated as binary
+*.exe binary
+*.jpg binary
+*.xl* binary
+*.pfx binary
+*.png binary
+*.dll binary
+*.so  binary

.github/ISSUE_TEMPLATE/1-bug.yaml

@@ -0,0 +1,35 @@
+name: Bug Report
+description: File a bug report
+title: "[Bug]: "
+labels: ["bug", "needs-triage"]
+projects: ["CyberShell-App/2"]
+assignees:
+  - fslef
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report!
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: Also tell us, what did you expect to happen?
+      placeholder: Tell us what you see!
+      value: "A bug happened!"
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
+      render: shell
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/CyberShell-App/CyberShell/blob/main/CODE_OF_CONDUCT.md)
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/ISSUE_TEMPLATE/2-feature-request.yaml

@@ -0,0 +1,37 @@
+name: Feature request
+description: File a new feature request
+labels: ["enhancement", "needs-triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report!
+  - type: textarea
+    id: feature
+    attributes:
+      label: Feature description
+      description: Please describe the behavior you'd like to see.
+    validations:
+      required: true
+  - type: textarea
+    id: problem-usecase
+    attributes:
+      label: Problem or use case
+      description: Please explain which problem this would solve, or what the use case is for the feature. Keep in mind that it's more likely to be implemented if it's generally useful for a larger number of users.
+    validations:
+      required: true
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives or workarounds
+      description: Please describe any alternatives or workarounds you have considered and, possibly, rejected.
+    validations:
+      required: true
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/CyberShell-App/CyberShell/blob/main/CODE_OF_CONDUCT.md)
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: "CyberSocForce GitHub discussion channel"
+    url: https://dsccommunity.org/community/contact/
+    about: "For any quesitons of to share your thought about this powershell module, please visit the GitHub discussion channel."

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,103 @@
+# Pull Request
+
+<!--
+    Thanks for submitting a Pull Request (PR) to this project.
+    Your contribution to this project is greatly appreciated!
+
+    TITLE: Please be descriptive not sensationalist.
+    Prepend the title with [BREAKING CHANGE] if relevant.
+    i.e. [BREAKING CHANGE] Restructure security data format
+
+    You may remove this comment block, and the other comment blocks, but please
+    keep the headers and the task list.
+    Try to keep your PRs atomic: changes grouped in smallest batch affecting a single logical unit.
+-->
+
+## Pull Request (PR) description
+
+<!--
+    Replace this comment block with a description of your PR to provide context.
+    Please be describe the intent and link issue where the problem has been discussed.
+    try to link the issue that it fixes by providing the verb and ref: [fix|close #18]
+
+    After the description, please concisely list the changes as per keepachangelog.com
+    This **should** duplicate what you've updated in the changelog file.
+
+### Added
+- for new features [closes #15]
+### Changed
+- for changes in existing functionality.
+### Deprecated
+- for soon-to-be removed features.
+### Security
+- in case of vulnerabilities.
+### Fixed
+- for any bug fixes. [fix #52]
+### Removed
+- for now removed features.
+-->
+
+## Task list
+
+<!--
+    To aid community reviewers in reviewing and merging your PR, please take
+    the time to run through the below checklist and make sure your PR has
+    everything updated as required.
+
+    Change to [x] for each task in the task list that applies to your PR.
+    For those task that don't apply to you PR, leave those as is.
+-->
+
+- [ ] The PR represents a single logical change.
+- [ ] Added an entry under the Unreleased section of in the CHANGELOG.md as per [format](https://keepachangelog.com/en/1.0.0/).
+- [ ] Local clean build passes without issue or fail tests (`build.ps1 -ResolveDependency`).
+- [ ] Documentation added/updated in src/WikiSource.
+- [ ] Comment-based help added/updated to any .ps1 files..
+- [ ] Unit tests added/updated. See [CyberShell Module Testing Guidelines](https://github.com/PowerShell/DscResources/blob/master/TestsGuidelines.md).
+- [ ] Integration tests added/updated (where possible). See [CyberShell Module Testing Guidelines](https://github.com/PowerShell/DscResources/blob/master/TestsGuidelines.md).
+
+
+
+
+-------------
+# Pull Request
+
+<!--
+Thank you for contributing! Please use a descriptive title and fill out this template to ensure a thorough review process.
+
+**Title Guidelines**: Be clear and succinct. Use the prefix [BREAKING CHANGE] for significant updates.
+
+-->
+
+## PR Description
+
+<!-- Briefly describe your changes, details will be provided in next section -->
+
+### Changes
+<!--
+list the changes as per keepachangelog.com This **should** duplicate what you've updated in the changelog file.`.
+
+### Added
+- New features.
+### Changed
+- Updates to existing functionality.
+### Deprecated
+- Features marked for removal.
+### Security
+- Security fixes.
+### Fixed
+- Bug fixes.
+### Removed
+- Removed features or code.
+-->
+
+## Checklist
+
+- [ ] Single logical change.
+- [ ] Changelog updated (Unreleased section as per keepachangelog.com).
+- [ ] Build passes (`build.ps1 -ResolveDependency`).
+- [ ] Documentation updated in `src/WikiSource`.
+- [ ] Comment-based help in `.ps1` files.
+- [ ] Unit and integration tests updated/added.
+
+<!-- Your contribution is appreciated! - Thank you->

.github/dependabot.yml

@@ -0,0 +1,11 @@
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for all configuration options:
+# https://docs.github.com/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file
+
+version: 2
+updates:
+  - package-ecosystem: "github-actions" # See documentation for possible values
+    directory: "/" # Location of package manifests
+    schedule:
+      interval: "weekly"