Enhance Nova CLI commands with improved feedback and error handling#236
Merged
stiwicourage merged 20 commits intoMay 24, 2026
Conversation
Add source-mirrored, dot-source-first Pester test files for the small and well-isolated helpers under src/private/scaffold and src/private/update so each unit-level helper has a focused test file under tests/private/scaffold or tests/private/update instead of being covered only through broad legacy coverage files. The remaining workflow-level scaffold and update helpers stay covered by the existing broad tests for now.
…package-align-with-terminal-ux-design-principles * develop: Restore and clarify deploy help links and update tests (#234) # Conflicts: # CHANGELOG.md # RELEASE_NOTE.md
…t steps guidance
…edback and clearer cancellation guidance
… and error messages refactor(Invoke-NovaCli): align with terminal-ux-design principles Fixes #222
…t-step guidance refactor(Invoke-NovaRelease): align with terminal-ux-design principles Fixes #223
…next-step guidance refactor(New-NovaModulePackage): align with terminal-ux-design principles Fixes #224
…t-step guidance refactor(Publish-NovaModule): align with terminal-ux-design principles Fixes #225
…upport and improved messaging refactor(Set-NovaUpdateNotificationPreference): align with terminal-ux-design principles Fixes #226
…ble guidance in WhatIf mode refactor(Test-NovaBuild): align with terminal-ux-design principles Fixes #227
…hatIf support refactor(Update-NovaModuleTools): align with terminal-ux-design principles Fixes #228
…d detailed summaries refactor(Update-NovaModuleVersion): align with terminal-ux-design principles Fixes #229
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
![codescene-delta-analysis[bot]](https://avatars.githubusercontent.com/in/53921?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
…g coverage and status messaging
There was a problem hiding this comment.
Gates Passed
See analysis details in CodeScene
Quality Gate Profile: Pay Down Tech Debt
Install CodeScene MCP: safeguard and uplift AI-generated code. Catch issues early with our IDE extension and CLI tool.
There was a problem hiding this comment.
Code Coverage Gates Passed
(required = 95%)
(required = 99%)
Review details by gate
-
Overall Coverage
- Pass/Fail Reason:
The overall coverage gate was checked for all code and meets the goal: 99.5% covered >= threshold = 95% - Action:
You have 292 files with a sum of 3732 covered and 18 uncovered lines of code.
- Pass/Fail Reason:
-
New & Changed Code Coverage
- Pass/Fail Reason:
New or changed code meets coverage goal: 99.8% covered >= threshold = 99% - Action:
You modified 17 files, and covered 507 added/modified lines of code.
- Pass/Fail Reason:
stiwicourage
deleted the
feature/215-refactordeploy-novapackage-align-with-terminal-ux-design-principles
branch
May 24, 2026 15:04
22 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Affected area
Review guidance
Validation
Validation notes:
Reviewed the actual diff against develop and checked CHANGELOG.md, RELEASE_NOTE.md, project.json,
.github/pull_request_template.md, .github/workflows/Publish.yml, README.md, CONTRIBUTING.md,
touched help files, and touched tests.
Executed targeted Pester coverage for the changed workflow surfaces:
publish, version update, self-update, notification preference, scaffold
Result:
Not run during release-summary prep:
Documentation and release follow-up
Maintainability, compatibility, and risk
Risk, rollout, or rollback notes:
Stable/prerelease semantics are unchanged: Publish.yml still treats main as the stable release branch
and develop as the prerelease branch, and project.json versioning was not changed in this diff.
Release-facing impact applies to both channels once shipped, but this branch will reach users through
the develop preview flow first. The unreleased CHANGELOG.md and RELEASE_NOTE.md entries match the
observed workflow/help changes; RELEASE_NOTE.md already has real entries (no placeholder) and no
compare-link footer URLs.
Highest operational risk is in publish/release/self-update/version flows because the changes alter
WhatIf, cancellation, progress, and result-summary behavior around real release operations. The Pester
coverage is good, but it is mostly mocked workflow validation, so one manual smoke pass for:
would still be prudent before cutting or promoting a release.
[!IMPORTANT]
Do not use a public pull request to disclose a vulnerability before coordinated handling.
Use the private reporting path in SECURITY.md for new security issues.