Auto Publish – main to live - 2026-01-02 23:00 UTC #12628
Merged
Conversation
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
* Clarify experimental feature is mainstream Previous verbiage in about_Pipelines wasn't clear that PSNativeCommandPreserveBytePipe is mainstream in PS 7.4. * Fix wrong feature link in 7.4 release notes PSNativeCommandPreserveBytePipe was using the wrong link reference (10 rather than 11). The linked doc has also been changed to `about_Pipelines`, as this explicitly mentions the (now mainstream) feature by name. * Apply suggestions from review --------- Co-authored-by: Mikey Lombardi (He/Him) <michael.t.lombardi@gmail.com>
* Fix 5.1 about_Format.ps1xml examples This fixes the wrong path used in both `Update-FormatData` examples. The paths used to initially create the custom formatting files are .\MyDotNetTypes.Format.ps1xml and .\MyFileSystem.Format.ps1xml. Before this change, Update-FormatData -PrependPath incorrectly pointed to $HOME\Format\CultureInfo.Format.ps1xml and $PSHOME\Format\MyFileSystem.Format.ps1xml. * Use consistent paths in 7.x about_Format.ps1xml Both Update-FormatData examples now use the $HOME\Format example path. This also updates the first example to create the directory before calling Export-FormatData, as the directory doesn't exist by default and Export-FormatData fails if part of the path is missing. * Minor style changes * Specify the correct formatting file extension This fixes the incorrect assertion that formatting files **must** use `.format.ps1xml` (only `.ps1xml` is required). * Adjust formatting file signing note The original note suggests that after copying Win PS formatting files, the signature block should be replaced. However, the files don't actually contain a signature block to begin with. This may cause confusion, so the note is updated with a more generalized suggestion on signing taken from about_Format.ps1xml. Also includes minor style changes and less Windows-specific references. * Use the same example path in all doc versions The 7.x docs use `$HOME\Format` as an example directory. This updates the 5.1 doc to use the same path. It also removes the suggestion to place custom formatting files in Win PS's `$PSHOME`. As this is a system directory, it's not an appropriate location for user files. * Fix formatting * Fix link references * Fix link references again * Apply suggestions from review --------- Co-authored-by: Mikey Lombardi (He/Him) <michael.t.lombardi@gmail.com>
* Update CSV cmdlet -Delimiter param description This clarifies the deserialization behavior when the specified delimiter doesn't match the actual delimiter in the input data. Before this change, the verbiage for Import/ConvertFrom-Csv implied one or more strings would be returned, which isn't the case. This also adds the existing note regarding escaped special characters to all docs. Previously, this was only present in Import-Csv docs, but is applicable to/useful for all CSV cmdlets. * Apply suggestions from review --------- Co-authored-by: Mikey Lombardi (He/Him) <michael.t.lombardi@gmail.com>
learn-build-service-prod
bot
requested review from
michaeltlombardi and
sdwheeler
as code owners
Contributor
Author
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
Contributor
Author
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.
This PR was automatically created by Auto Publish system to publish changes from the main branch to the live branch.