Skip to content

Fix example for mount path file reference#128253

Open
georgeOsdDev wants to merge 1 commit intoMicrosoftDocs:mainfrom
georgeOsdDev:patch-10
Open

Fix example for mount path file reference#128253
georgeOsdDev wants to merge 1 commit intoMicrosoftDocs:mainfrom
georgeOsdDev:patch-10

Conversation

@georgeOsdDev
Copy link
Contributor

This pull request corrects a documentation example to clarify the usage of file paths when mounting storage in container apps.

  • Documentation fix:
    • Corrected the example to use consistent file names for both the sub path and mount path, ensuring clarity that the mount path should refer to a file that does not already exist in the container.

@prmerger-automator
Copy link
Contributor

@georgeOsdDev : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit d7afbeb:

✅ Validation status: passed

File Status Preview URL Details
articles/container-apps/storage-mounts.md ✅Succeeded

For more details, please refer to the build report.

@ttorble ttorble requested a review from Copilot February 26, 2026 15:15
Copy link
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

This PR corrects a documentation example to ensure consistency in file path naming conventions when mounting storage in container apps. The fix clarifies that the mount path should include the complete file path with extension when referring to a file.

Changes:

  • Updated the mount path example to include the .txt extension, matching the format used in the sub path example

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

@ttorble
Copy link
Contributor

ttorble commented Feb 26, 2026

@craigshoemaker

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Feb 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants