Skip to content

Conversation

@mathewc
Copy link
Contributor

@mathewc mathewc commented Jan 7, 2026

No description provided.

@prmerger-automator
Copy link
Contributor

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

> [Run your functions from a package file in Azure](run-functions-from-deployment-package.md)
[.zip push deployment reference topic]: https://github.com/projectkudu/kudu/wiki/Deploying-from-a-zip-file
[.zip push deployment reference topic]: https://github.com/projectkudu/kudu/wiki/Deploying-from-a-zip-file-or-url
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I fixed this one as well, but I don't actually see this content at https://learn.microsoft.com/en-us/azure/azure-functions/deployment-zip-push#deployment-zip-file-requirements. Should this line just be removed?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah, I'll take care of that....thanks @mathewc

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 9e54d66:

✅ Validation status: passed

File Status Preview URL Details
articles/azure-functions/deployment-zip-push.md ✅Succeeded

For more details, please refer to the build report.

@v-dirichards v-dirichards requested a review from Copilot January 7, 2026 21:56
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 fixes a broken wiki link in the Azure Functions deployment documentation by updating the URL path from the old format to the new format that includes "-or-url" suffix.

  • Updated two instances of the Kudu wiki link to point to the correct URL path

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

@v-dirichards
Copy link
Contributor

Hi @mathewc - This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge, but would you make future content updates in the private repo? Thank you!


@ggailey777

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 Jan 7, 2026
@mathewc
Copy link
Contributor Author

mathewc commented Jan 8, 2026

@v-dirichards Do you mean team members should instead contribute via the azure-docs-pr repo? I can do that next time.

@v-dirichards
Copy link
Contributor

@mathewc Correct. Microsoft authors and contributors need to make content contributions through the private repository so the content can be staged and validated by the current validation rules.

@ggailey777
Copy link
Contributor

@mathewc I've moved your commit over to my open PR in the private repo.: https://github.com/MicrosoftDocs/azure-docs-pr/pull/309800 #please-close this public PR.

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.

3 participants