Problem
The repository still relies on a legacy Azure DevOps pipeline (azure-pipelines.yml) using deprecated phase syntax and outdated hosted images. This creates drift from the rest of AtlassianPS and makes CI maintenance harder.
Proposal
Introduce a GitHub Actions CI workflow equivalent to the current build/test coverage, modeled after JiraPS conventions:
- separate lint/build/test jobs
- artifact handoff between jobs
- multi-OS test matrix (Windows PowerShell 5.1 + pwsh on Windows/Linux/macOS)
- required aggregate CI result job for branch protection
Acceptance criteria
Problem
The repository still relies on a legacy Azure DevOps pipeline (
azure-pipelines.yml) using deprecated phase syntax and outdated hosted images. This creates drift from the rest of AtlassianPS and makes CI maintenance harder.Proposal
Introduce a GitHub Actions CI workflow equivalent to the current build/test coverage, modeled after JiraPS conventions:
Acceptance criteria
.github/workflows/ci.ymlexists and runs on PRs and pushes tomasterazure-pipelines.ymlis removed or explicitly deprecated after parity confirmation