feat: ollama-powershell core ( Fixes #1 )

Isolating existing code into new module

Author: James Brundage

Build/GitHub/Jobs/BuildOllamaPowerShell.psd1

@@ -0,0 +1,40 @@
+@{
+    "runs-on" = "ubuntu-latest"    
+    if = '${{ success() }}'
+    steps = @(
+        @{
+            name = 'Check out repository'
+            uses = 'actions/checkout@v2'
+        }
+        @{
+            name = 'GitLogger'
+            uses = 'GitLogging/GitLoggerAction@main'
+            id = 'GitLogger'
+        }
+        @{
+            name = 'Use PSSVG Action'
+            uses = 'StartAutomating/PSSVG@main'
+            id = 'PSSVG'
+        }
+        @{
+            name = 'Use PipeScript Action'
+            uses = 'StartAutomating/PipeScript@main'
+            id = 'PipeScript'
+        }
+        'RunEZOut'
+        'RunHelpOut'
+        <#,
+        @{
+            name = 'Use PSJekyll Action'
+            uses = 'PowerShellWeb/PSJekyll@main'
+            id = 'PSJekyll'
+        }#>
+        <#@{
+            name = 'Run WebSocket (on branch)'
+            if   = '${{github.ref_name != ''main''}}'
+            uses = './'
+            id = 'WebSocketAction'
+        },#>
+        # 'BuildAndPublishContainer'
+    )
+}

Build/GitHub/Steps/PublishTestResults.psd1

@@ -0,0 +1,10 @@
+@{
+    name = 'PublishTestResults'
+    uses = 'actions/upload-artifact@main'
+    with = @{
+        name = 'PesterResults'
+        path = '**.TestResults.xml'
+    }
+    if = '${{always()}}'
+}
+

Build/ollama-powershell.GitHubWorkflow.PSDevOps.ps1

@@ -0,0 +1,15 @@
+#requires -Module PSDevOps
+Import-BuildStep -SourcePath (
+    Join-Path $PSScriptRoot 'GitHub'
+) -BuildSystem GitHubWorkflow
+
+Push-Location ($PSScriptRoot | Split-Path)
+New-GitHubWorkflow -Name "Build ollama-powershell" -On Push,
+    PullRequest, 
+    Demand -Job  TestPowerShellOnLinux, 
+    TagReleaseAndPublish, BuildOllamaPowerShell -Environment ([Ordered]@{
+        REGISTRY = 'ghcr.io'
+        IMAGE_NAME = '${{ github.repository }}'
+    }) -OutputPath .\.github\workflows\BuildOllamaPowerShell.yml
+
+Pop-Location

Build/ollama-powershell.ezout.ps1

@@ -0,0 +1,39 @@
+#requires -Module EZOut
+#  Install-Module EZOut or https://github.com/StartAutomating/EZOut
+$myFile = $MyInvocation.MyCommand.ScriptBlock.File
+$myRoot = $myFile | Split-Path | Split-Path
+$myModuleName = $myFile | Split-Path | Split-Path | Split-Path -Leaf
+Push-Location $myRoot
+$formatting = @(
+    # Add your own Write-FormatView here,
+    # or put them in a Formatting or Views directory
+    foreach ($potentialDirectory in 'Formatting','Views','Types') {
+        Join-Path $myRoot $potentialDirectory |
+            Get-ChildItem -ea ignore |
+            Import-FormatView -FilePath {$_.Fullname}
+    }
+)
+
+$destinationRoot = $myRoot
+
+if ($formatting) {
+    $myFormatFilePath = Join-Path $destinationRoot "$myModuleName.format.ps1xml"
+    # You can also output to multiple paths by passing a hashtable to -OutputPath.
+    $formatting | Out-FormatData -Module $MyModuleName -OutputPath $myFormatFilePath
+}
+
+$types = @(
+    # Add your own Write-TypeView statements here
+    # or declare them in the 'Types' directory
+    Join-Path $myRoot Types |
+        Get-Item -ea ignore |
+        Import-TypeView
+
+)
+
+if ($types) {
+    $myTypesFilePath = Join-Path $destinationRoot "$myModuleName.types.ps1xml"
+    # You can also output to multiple paths by passing a hashtable to -OutputPath.
+    $types | Out-TypeData -OutputPath $myTypesFilePath
+}
+Pop-Location

CODE_OF_CONDUCT.md

@@ -0,0 +1,9 @@
+# Code of Conduct
+
+We have a simple subjective code of conduct:
+
+1. Be Respectful
+2. Be Helpful
+3. Do No Harm
+
+Failure to follow the code of conduct may result in blocks or banishment.

CONTRIBUTING.md

@@ -0,0 +1,18 @@
+# Contributing
+
+## Who Can Contribute?
+
+We welcome all contributions, as long as they're related to using ollama and PowerShell.
+
+## What Can I Contribute?
+
+You can contribute issues and pull requests containing new PowerShell functions or documentation.
+
+We welcome integrations with any AI APIs and tools out there.
+
+## Why Contribute?
+
+You should contribute to help the community, and share your knowledge.  
+
+This module is meant to be a grab bag of AI fun in PowerShell,
+and your contribution can bring more joy and knowledge to the world.