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-11-21] [METADATA UPDATE] Populating missing meta descriptions #212

Merged
merged 2 commits into from
Nov 8, 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 [email protected]. 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#921050 AI generated meta-descriptions batch-Nov

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.

Copy link
Contributor Author

Learn Build status updates of commit ebcf460:

✅ Validation status: passed

File Status Preview URL Details
dynamics-nav-app/across-how-find-posted-documents-without-income-document-records.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@edupont04 edupont04 self-assigned this Nov 8, 2023
@edupont04
Copy link
Collaborator

The article already had the required metadata property but with a capital D.... Updted accordingly.

Copy link
Contributor Author

Learn Build status updates of commit 3c8dc40:

✅ Validation status: passed

File Status Preview URL Details
dynamics-nav-app/across-how-find-posted-documents-without-income-document-records.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@edupont04 edupont04 merged commit 2c1a640 into main Nov 8, 2023
3 checks passed
@edupont04 edupont04 deleted the ef8adc57-b19e-45a4-a886-85d3319a4b5b_40 branch November 8, 2023 09:32
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.

1 participant