Skip to content

(AB-538640) Clarify behavior of Rename-Item when new name item exists#12915

Merged
sdwheeler merged 1 commit intoMicrosoftDocs:mainfrom
michaeltlombardi:ab-538640/main/rename-item-exists
Apr 1, 2026
Merged

(AB-538640) Clarify behavior of Rename-Item when new name item exists#12915
sdwheeler merged 1 commit intoMicrosoftDocs:mainfrom
michaeltlombardi:ab-538640/main/rename-item-exists

Conversation

@michaeltlombardi
Copy link
Copy Markdown
Contributor

@michaeltlombardi michaeltlombardi commented Apr 1, 2026

PR Summary

This change fixes AB#538640 by clarifying the behavior of Rename-Item when the new name for the item already exists and that Rename-Item -Force doesn't replace the existing item.

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 contributor's guide.
  • Style: This PR adheres to the style guide.

Copilot AI review requested due to automatic review settings April 1, 2026 17:13
@learn-build-service-prod

This comment was marked as outdated.

@learn-build-service-prod

This comment was marked as outdated.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates Rename-Item reference docs to clarify that renaming to an already-existing name does not replace the destination item, including when -Force is used.

Changes:

  • Add narrative guidance that Rename-Item cannot replace an existing destination name and suggest Move-Item -Force instead.
  • Clarify -Force parameter behavior to explicitly note it doesn’t replace an existing item named by -NewName.
  • Refresh ms.date metadata across supported versioned references.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File Description
reference/7.6/Microsoft.PowerShell.Management/Rename-Item.md Adds/clarifies guidance around non-overwriting rename behavior and updates metadata date.
reference/7.5/Microsoft.PowerShell.Management/Rename-Item.md Same clarification for 7.5 docs plus metadata date update.
reference/7.4/Microsoft.PowerShell.Management/Rename-Item.md Same clarification for 7.4 docs plus metadata date update.
reference/5.1/Microsoft.PowerShell.Management/Rename-Item.md Same clarification for Windows PowerShell 5.1 docs plus metadata date update.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@michaeltlombardi michaeltlombardi force-pushed the ab-538640/main/rename-item-exists branch from 292e26a to 83e64a3 Compare April 1, 2026 17:36
@learn-build-service-prod
Copy link
Copy Markdown
Contributor

PoliCheck Scan Report

The 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 found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 83e64a3:

✅ Validation status: passed

File Status Preview URL Details
reference/5.1/Microsoft.PowerShell.Management/Rename-Item.md ✅Succeeded View (powershell-5.1)
reference/7.4/Microsoft.PowerShell.Management/Rename-Item.md ✅Succeeded View (powershell-7.4)
reference/7.5/Microsoft.PowerShell.Management/Rename-Item.md ✅Succeeded View (powershell-7.5)
reference/7.6/Microsoft.PowerShell.Management/Rename-Item.md ✅Succeeded View (powershell-7.6)

For more details, please refer to the build report.

Copy link
Copy Markdown
Collaborator

@sdwheeler sdwheeler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@sdwheeler sdwheeler merged commit 5d9f217 into MicrosoftDocs:main Apr 1, 2026
5 checks passed
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.

3 participants