Update path filters for Windows CI

[TravisEz13]

PR Summary

This pull request updates the pr: section of the .vsts-ci/windows.yml file to refine the paths that trigger the CI pipeline. The primary changes include narrowing down the included paths and expanding the excluded paths.

Changes to CI pipeline paths:

• Included paths have been refined to specific directories and files such as src/*, .vsts-ci/windows.yml, .vsts-ci/templates/*, test/*, build.psm1, tools/buildCommon/*, tools/ci.psm1, and tools/WindowsCI.psm1.
• Excluded paths have been expanded to include various configuration and documentation files, such as .dependabot/config.yml, .github/ISSUE_TEMPLATE/*, .github/workflows/*, .vsts-ci/misc-analysis.yml, tools/cgmanifest.json, LICENSE.txt, test/common/markdown/*, test/perf/*, tools/packaging/*, tools/releaseBuild/*, tools/releaseBuild/azureDevOps/templates/*, README.md, .spelling, and .pipelines/*.

PR Context

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Experimental feature(s) needed
    • Experimental feature name(s):
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    - [ ] Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:
    • Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
      (which runs in a different PS Host).
      • Issue filed:
    • Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
      • Issue filed:
    • Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
      • Issue filed:
    • Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).
      • Issue filed:

[TravisEz13]

/azp run PowerShell-CI-macos, PowerShell-CI-Linux, PowerShell-CI-Windows, PowerShell-CI-static-analysis, PSResourceGet ACR, PowerShell-Windows-Packaging-CI

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[microsoft-github-policy-service]

📣 Hey @TravisEz13, how did we do? We would love to hear your feedback with the link below! 🗣️

🔗 https://aka.ms/PSRepoFeedback

Microsoft Forms

[TravisEz13]

/backport to release/v7.5

[github-actions]

Started backporting to release/v7.5: https://github.com/PowerShell/PowerShell/actions/runs/13578689281

GitHub

Update path filters for Windows CI · PowerShell/PowerShell@0f7c8de

PowerShell for every system! Contribute to PowerShell/PowerShell development by creating an account on GitHub.

[github-actions]

@TravisEz13 an error occurred while backporting to "release/v7.5", please check the run log for details!

GitHub Actions is not permitted to create or approve pull requests.