Fixes the GitHub Actions workflow to properly handle the PSSpecKit module structure and testing. ## Changes Made - **PSScriptAnalyzer Scope**: Updated the workflow to scan only the `./PSSpecKit` module directory instead of the entire repository, avoiding unnecessary scanning of development/debug scripts in `tools/` - **Module Import Verification**: Added an explicit step to verify the module can be imported successfully and displays all exported functions before running tests - **Workflow Cleanup**: Removed commented-out code for cleaner workflow definition ## Testing - ✅ PSScriptAnalyzer runs successfully on the module directory - ✅ Module imports correctly with all 6 functions exported - ✅ All 21 Pester tests pass (unit and integration tests) - ✅ Workflow properly validates module structure before running tests The workflow now focuses on testing the module itself rather than scanning development scripts, ensuring proper validation of the module structure and functionality. <details> <summary>Original prompt</summary> > > ---- > > *This section details on the original issue you should resolve* > > <issue_title>Fix workflow for testing module files</issue_title> > <issue_description>Fix the Action workflow and supporting files to handle properly the module and its files. </issue_description> > > ## Comments on the Issue (you are @copilot in this section) > > <comments> > </comments> > </details> Fixes #8  <details> <summary>Original prompt</summary> > > ---- > > *This section details on the original issue you should resolve* > > <issue_title>Fix workflow for testing module files</issue_title> > <issue_description>Fix the Action workflow and supporting files to handle properly the module and its files. </issue_description> > > ## Comments on the Issue (you are @copilot in this section) > > <comments> > </comments> > </details> Fixes #8  --- ✨ Let Copilot coding agent [set things up for you](https://github.com/johnmbaughman/PSSpecKit/issues/new?title=✨+Set+up+Copilot+instructions&body=Configure%20instructions%20for%20this%20repository%20as%20documented%20in%20%5BBest%20practices%20for%20Copilot%20coding%20agent%20in%20your%20repository%5D%28https://gh.io/copilot-coding-agent-tips%29%2E%0A%0A%3COnboard%20this%20repo%3E&assignees=copilot) — coding agent works faster and does higher quality work when set up for your repo. --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: johnmbaughman <1634414+johnmbaughman@users.noreply.github.com>

Fix workflow for testing module files #8

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions