Skip to content

[METADATA UPDATE] Unified User Feedback - Wave 1#149

Merged
lindalu-MSFT merged 1 commit intomainfrom
52e1d2f8-edf9-4733-8b1f-35554d316113_3
May 11, 2023
Merged

[METADATA UPDATE] Unified User Feedback - Wave 1#149
lindalu-MSFT merged 1 commit intomainfrom
52e1d2f8-edf9-4733-8b1f-35554d316113_3

Conversation

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

As part of the Unified User Feedback program, the new Thumbs Up/Down feedback experience will be enabled in repos that are part of Wave 1.

Wave 1: Teams who don't have the GH (GitHub) Issues widget enabled

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 UserFeedbackTeam@microsoft.com. If you are not the correct contact for this content and repository, please notify Metadata-Management@microsoft.com.

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 Metadata-Management@microsoft.com if you have questions or concerns or would like Pull Requests for metadata updates to merge automatically in future.

Fixing#812888 Batch update feedback_system=Standard 8

What metadata are we updating for our feedback system and why
Please refer to slides 27 and 28 of the readiness plan.

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.

…erence, MicrosoftDocs--win32, MicrosoftDocs--windows-iot, mono--SkiaSharp-API-docs, OfficeDev--office-dev-program-docs, OfficeDev--open-xml-docs-ref-dotnet, xamarin--apple-api-docs
@learn-build-service-prod
Copy link
Copy Markdown
Contributor Author

Learn Build status updates of commit ba2c36d:

✅ Validation status: passed

File Status Preview URL Details
docs/docfx.json ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@lindalu-MSFT lindalu-MSFT merged commit 7f6c6e6 into main May 11, 2023
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