Skip to content
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

[METADATA UPDATE][Merge by 2023-10-04] [METADATA UPDATE] Populating missing meta descriptions #222

Merged
merged 1 commit into from
Sep 25, 2023

Conversation

learn-build-service-prod[bot]
Copy link
Contributor

A Pull Request has been made from the Learn Platform's Metadata Management System. Please review and merge this Pull Request within 5 days. If you have any questions or concerns about the purpose of these metadata updates, please contact lmagarinos. If you are not the correct contact for this content and repository, please notify [email protected].

If this Pull Request is not merged within 14 days, it will be automatically merged by our system to ensure the timeliness of the metadata update. This includes bypassing the Repository's Branch Policy, including if Review Required is enabled. Please notify [email protected] if you have questions or concerns or would like Pull Requests for metadata updates to merge automatically in future.

Fixing#878076 AI generated meta-descriptions batch-2

Why we make metadata updates?
This pull request will populate missing meta descriptions. Optimized meta descriptions are critical for good SEO including click-through-rates and user experience. This project is focused on testing the use of AI generated outputs in the remediation of content with missing data.

How does this affect me?
After you review and accept the proposed meta descriptions, the new meta descriptions will be populated and available in search results for impacted URLs improving SEO and UX.

Frequently Asked Questions
Why does this Pull Request appear to be made by the Repository Owner? We open Pull Requests two different ways.

  • For Git Repos with a permissioned Service Account, we open the PR from our Document Build Service Account.
  • For Git Repos that we either do not have Service Account permission for or the repo is in Azure Repos (ADO) we open the Pull Requests in an automated way with the PR creator as the Repo owner.

How can I revert a Pull Request that has been merged and created an unexpected issue? Whether a PR has been merged manually or automatically, you can revert it if an issue arises. See Reverting a pull request - GitHub Docs.

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

Learn Build status updates of commit 29f3cdc:

💡 Validation status: suggestions

File Status Preview URL Details
msal-dotnet-articles/advanced/extensibility-points.md 💡Suggestion View Details
msal-dotnet-articles/advanced/exceptions/broker.md ✅Succeeded View
msal-dotnet-articles/advanced/exceptions/index.md ✅Succeeded View
msal-dotnet-articles/advanced/exceptions/retry-policy.md ✅Succeeded View
msal-dotnet-articles/advanced/exceptions/unity.md ✅Succeeded View
msal-dotnet-articles/advanced/high-availability.md ✅Succeeded View
msal-dotnet-articles/advanced/performance-testing.md ✅Succeeded View
msal-dotnet-articles/resources/known-issues.md ✅Succeeded View
msal-dotnet-articles/resources/telemetry-overview.md ✅Succeeded View
msal-dotnet-articles/resources/troubleshooting.md ✅Succeeded View

msal-dotnet-articles/advanced/extensibility-points.md

  • Line 12, Column 82: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /aspnet/core/fundamentals/http-requests?view=aspnetcore-6.0
  • Line 53, Column 9: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /dotnet/api/microsoft.identity.client.abstractacquiretokenparameterbuilder-1.withextraqueryparameters?view=azure-dotnet#microsoft-identity-client-abstractacquiretokenparameterbuilder-1-withextraqueryparameters(system-string)
  • Line 59, Column 9: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /dotnet/api/microsoft.identity.client.extensibility.icustomwebui?view=azure-dotnet

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

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

Learn Build status updates of commit 29f3cdc:

💡 Validation status: suggestions

File Status Preview URL Details
msal-dotnet-articles/advanced/extensibility-points.md 💡Suggestion View Details
msal-dotnet-articles/advanced/exceptions/broker.md ✅Succeeded View
msal-dotnet-articles/advanced/exceptions/index.md ✅Succeeded View
msal-dotnet-articles/advanced/exceptions/retry-policy.md ✅Succeeded View
msal-dotnet-articles/advanced/exceptions/unity.md ✅Succeeded View
msal-dotnet-articles/advanced/high-availability.md ✅Succeeded View
msal-dotnet-articles/advanced/performance-testing.md ✅Succeeded View
msal-dotnet-articles/resources/known-issues.md ✅Succeeded View
msal-dotnet-articles/resources/telemetry-overview.md ✅Succeeded View
msal-dotnet-articles/resources/troubleshooting.md ✅Succeeded View

msal-dotnet-articles/advanced/extensibility-points.md

  • Line 12, Column 82: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /aspnet/core/fundamentals/http-requests?view=aspnetcore-6.0
  • Line 53, Column 9: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /dotnet/api/microsoft.identity.client.abstractacquiretokenparameterbuilder-1.withextraqueryparameters?view=azure-dotnet#microsoft-identity-client-abstractacquiretokenparameterbuilder-1-withextraqueryparameters(system-string)
  • Line 59, Column 9: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /dotnet/api/microsoft.identity.client.extensibility.icustomwebui?view=azure-dotnet

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

@localden localden merged commit 6c0c664 into main Sep 25, 2023
@localden localden deleted the 4d5dcd85-1d0d-4503-98d8-3916b4e3c94b_77 branch September 25, 2023 19:33
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.

2 participants