Skip to content

Conversation

deadlydog
Copy link
Contributor

PR Summary

There is a bug in Windows PowerShell 5.1 with the Get-ChildItem cmdlet where it ignores the -Depth parameter when it is used with the -Include parameter. There is a GitHub repo to easily reproduce this issue here.

This change adds a note to the documentation to make the unexpected behaviour more well-known.

PR Checklist

  • Descriptive Title: This PR's title is a synopsis of the changes it proposes.
  • Summary: This PR's summary describes the scope and intent of the change.
  • Contributor's Guide: I have read the contributors guide.
  • Style: This PR adheres to the style guide.

Copy link
Contributor

Learn Build status updates of commit 9d7f882:

✅ Validation status: passed

File Status Preview URL Details
reference/5.1/Microsoft.PowerShell.Management/Get-ChildItem.md ✅Succeeded View (powershell-5.1)

For more details, please refer to the build report.

For any questions, please:

Copy link

Expectations

Thanks for your submission! Here's a quick note to provide you with some context for what to expect from the docs team and the process now that you've submitted a PR. Even if you've contributed to this repo before, we strongly suggest reading this information; it might have changed since you last read it.

To see our process for reviewing PRs, please read our editor's checklist and process for managing pull requests in particular. Below is a brief, high-level summary of what to expect, but our contributor guide has expanded details.

The docs team begins to review your PR if you request them to or if your PR meets these conditions:

  • It is not a draft PR.
  • It does not have a WIP prefix in the title.
  • It passes validation and build steps.
  • It does not have any merge conflicts.
  • You have checked every box in the PR Checklist, indicating you have completed all required steps and marked your PR as Ready to Merge.

You can always request a review at any stage in your authoring process, the docs team is here to help! You do not need to submit a fully polished and finished draft; the docs team can help you get content ready for merge.

While reviewing your PR, the docs team may make suggestions, write comments, and ask questions. When all requirements are satisfied, the docs team marks your PR as Approved and merges it. Once your PR is merged, it is included the next time the documentation is published. For this project, the documentation is published daily at 3 p.m. Pacific Standard Time (PST).

This comment was marked as outdated.

@sdwheeler sdwheeler force-pushed the Windows51GetChildItemDepthIncludeBug branch from 9e1c2e0 to d073584 Compare February 18, 2025 15:28
Copy link
Contributor

Learn Build status updates of commit d073584:

✅ Validation status: passed

File Status Preview URL Details
reference/5.1/Microsoft.PowerShell.Management/Get-ChildItem.md ✅Succeeded View (powershell-5.1)

For more details, please refer to the build report.

For any questions, please:

@sdwheeler sdwheeler merged commit 0051103 into MicrosoftDocs:main Feb 18, 2025
4 checks passed
@sdwheeler
Copy link
Collaborator

@deadlydog Thanks for the updates.

@deadlydog deadlydog deleted the Windows51GetChildItemDepthIncludeBug branch February 23, 2025 05:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants