Skip to content

Update functions-how-to-azure-devops to clear warning message #127376

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

nikmaxott
Copy link

Using prune --production gives a warning to switch to --omit=dev I have done this

Using prune --production gives a warning to switch to --omit=dev I have done this
Copy link
Contributor

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

@nikmaxott
Copy link
Author

nikmaxott commented Jul 14, 2025

Also as an aside, why are we publishing and then downloading to the artifacts, can we switch to just publishing and then using $(System.DefaultWorkingDirectory)/**/*.zip as the package. I am happy to create a PR for this change

Copy link
Contributor

Learn Build status updates of commit 34cc1bb:

✅ Validation status: passed

File Status Preview URL Details
articles/azure-functions/functions-how-to-azure-devops.md ✅Succeeded

For more details, please refer to the build report.

@v-dirichards
Copy link
Contributor

@juliakm

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 Jul 14, 2025
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