You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Introduced custom PSScriptAnalyzer rules in CustomRules module to enforce comment-based help, parameter descriptions, and proper casing.
- Created run-pssa.ps1 script to execute PSScriptAnalyzer with custom rules for public and non-public code.
- Added test.ps1 script for running Pester tests with coverage and detailed output.
- Documented the delivery and release process, development overview, quality gates, and troubleshooting steps in Markdown files.
- Established a structured branch model for development and release processes.
* Match the existing repository style and indentation.
10
+
* Use spaces for indentation and keep OTBS/K\&R brace style.
11
+
* Preserve comment-based help for public functions.
12
+
* Keep public cmdlet names, aliases, and manifest exports aligned with existing patterns.
13
+
* Prefer PowerShell 7-compatible solutions; this repo does not target Windows PowerShell 5.1.
14
+
* Preserve existing HaloAPI parameter naming conventions even if they are not camelCase.
15
+
* Treat helper classes, validators, argument transformations, and completers as part of the public module design surface and change them carefully.
16
+
* For test execution, do not add or use raw `Invoke-Pester` commands as the standard repo workflow; route test runs through `DevOps/Quality/test.ps1` instead.
description: "Use for CI/CD and automation changes in HaloAPI: keep workflows explicit, safe, and consistent with the GitHub Actions-based release flow."
* Prefer explicit failure handling in PowerShell workflow steps.
11
+
* Use the repo scripts (`Bootstrap.ps1`, `DevOps/Quality/run-pssa.ps1`, `DevOps/Quality/test.ps1`) instead of recreating logic inline in workflows.
12
+
* When making GitHub Actions changes, avoid broadening secrets usage or release scope unless explicitly requested.
13
+
* Preserve the repo's branch behavior: normal CI and pull request validation target `develop`, while stable releases are cut from `main`.
14
+
* Do not use raw `Invoke-Pester` as a workflow, terminal, or agent execution path for HaloAPI validation.
15
+
* Use `DevOps/Quality/test.ps1` as the only supported test entrypoint in CI and interactive tooling; direct Pester invocation is only allowed inside that dedicated script.
16
+
* Prefer dedicated script entrypoints over ad hoc analyzer commands in CI and interactive tooling.
0 commit comments