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-08-14] Populating missing meta descriptions #302

Merged

Conversation

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

A Pull Request has been made from the Learn Platform's Metadata Management System to update metadata. Please review and merge this Pull Request within 5 days.

  • If you are not the correct contact for this content and repository, please notify [email protected].
  • Please notify [email protected] if you have questions or concerns or would like Pull Requests for metadata updates to merge automatically in future.
  • If you have questions or concerns about these metadata changes, please contact [email protected] to let us know.

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.
Fixing#866292 [SEO] [AI] Create pull requests for 200 AI generated meta-descriptions (7/31) batch-1

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 86e123a:

✅ Validation status: passed

File Status Preview URL Details
Odata-docs/webapi/v6/customizable-type-facets-promotion.md ✅Succeeded View

For more details, please refer to the build report.

For any questions, please:

@learn-build-service-prod learn-build-service-prod bot merged commit b1ed5a3 into main Aug 14, 2023
@learn-build-service-prod learn-build-service-prod bot deleted the c0068fae-bc6c-44ba-9e68-8c4df8566709_50 branch August 14, 2023 11:42
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.

0 participants