(AB-538639) Add note for destination exists to Move-Item#12914
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
There was a problem hiding this comment.
Pull request overview
Updates Move-Item reference docs to clarify behavior when the destination already exists and to direct users to -Force for overwriting.
Changes:
- Add a note explaining the error condition when the destination item exists and suggesting
-Force. - Update
ms.datemetadata for affected versions.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| reference/7.6/Microsoft.PowerShell.Management/Move-Item.md | Adds “destination exists” guidance and updates ms.date. |
| reference/7.5/Microsoft.PowerShell.Management/Move-Item.md | Adds “destination exists” guidance and updates ms.date. |
| reference/7.4/Microsoft.PowerShell.Management/Move-Item.md | Adds “destination exists” guidance and updates ms.date. |
| reference/5.1/Microsoft.PowerShell.Management/Move-Item.md | Adds “destination exists” guidance and updates ms.date. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
michaeltlombardi
force-pushed
the
ab-538639/main/move-item-dest-exists
branch
from
702c401 to
fbdebe3
Compare
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 |
|
Learn Build status updates of commit fbdebe3: ✅ Validation status: passed
For more details, please refer to the build report. |
Co-authored-by: Sean Wheeler <sean.wheeler@microsoft.com>
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 |
|
Learn Build status updates of commit cd508c9: ✅ Validation status: passed
For more details, please refer to the build report. |
PR Summary
This change fixes AB#538639 by noting that the cmdlet fails if the destination item already exists and directs the reader to use the
-Forceparameter.PR Checklist