-
-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.7.1: Fix Build-PSBuildMarkdown + Lint Fixes #75
Draft
HeyItsGilbert
wants to merge
9
commits into
main
Choose a base branch
from
0.7.1
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
…and improve parameter formatting * Updated `[cmdletbinding()]` to `[CmdletBinding()]` for consistency. * Enhanced readability by aligning parameter assignments in `$newMDParams`. * Added new words to `cspell.json` for better spell checking.
* Migrate `ScriptAnalyzerSettings.psd1` to `tests` directory and update paths. * Enhance task definitions in `psakeFile.ps1` for better readability and consistency. * Add new exclusion rule for `PSUseApprovedVerbs` in the script analysis settings.
…andling and suppress warnings * Added suppression attributes for unused parameters in `Publish-PSBuildModule` and `Test-PSBuildPester`. * Enhanced `CmdletBinding` attribute casing for consistency. * Refined parameter validation logic for better clarity and maintainability.
…ate changelog * Remove extra item from `New-MarkdownHelp` splat to prevent failure with `$PSBPreference.Docs.Overwrite = $true` * Clean up failing Script Analyzer settings and relocate the configuration file.
…hance psake file * Introduced two new launch configurations for debugging PowerShell scripts in VSCode. * Updated `psakeFile.ps1` to correct property casing and added functionality to control documentation overwrite behavior. * Enhanced tests to verify the documentation overwrite feature.
* Build tests now run in TempDir * TestModule moved into fixtures folder. * Added test for docs
…cation` * Ensures proper stack management for directory changes in tests. * Improves cleanup in `AfterAll` by restoring the previous location.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
New-MarkdownHelp
splat that would result in a failurewhen using
$PSBPreference.Docs.Overwrite = $true
Description
There was an extra item being added to the hashtable. This resolves that.
This also addresses several scriptanalyzer warnings.
Related Issue
n\a
Motivation and Context
This fixes a failure scenario with the new Overwrite feature.
How Has This Been Tested?
Checklist: