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.

Sign up for GitHub

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

Jump to bottom

Feedback forum is closed #3701

Closed
gekka opened this issue Mar 4, 2022 · 1 comment
Closed

Feedback forum is closed #3701

gekka opened this issue Mar 4, 2022 · 1 comment
Assignees
@GrantMeStrength
Labels
doc-bug feedback is about something that is out of date, unclear, confusing, or broken in the article Pri1 publish/tech uwp/prod

Comments

@gekka
Copy link

gekka commented Mar 4, 2022

If you have feedback on the policies, please let us know by commenting in our forum. We will consider every comment.

Many forums in social.msdn.microsoft.com is closed, and moved to Q&A.
As a result, it is no longer possible feedback by current link.
No one can know where the correct link is now.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@drewbatgit drewbatgit added the doc-bug feedback is about something that is out of date, unclear, confusing, or broken in the article label Mar 24, 2022
learn-build-service-prod bot added a commit that referenced this issue Jul 31, 2023
@learn-build-service-prod
Merge pull request #3701 from MicrosoftDocs/main638264198183135150syn…
7bc7f70 
…c_temp

For protected CLA branch, push strategy should use PR and merge to target branch method to work around git push error
@jwmsft jwmsft assigned GrantMeStrength and unassigned hickeys Jan 11, 2024
@GrantMeStrength
Copy link
Contributor

We are changing the way we track issues filed from our documentation pages: please see this blog post for more details. The Microsoft Store documentation has been updated several times since your issue was reported, and there's a good chance your problem has been addressed. Right now, this issue is being closed but if you feel it is still valid and has not been addressed, please re-open it with any more available information. Please note that if you question is more general and not related to documentation, Microsoft Q&A is a great way to get questions answered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@GrantMeStrength GrantMeStrength

Labels
doc-bug feedback is about something that is out of date, unclear, confusing, or broken in the article Pri1 publish/tech uwp/prod
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@GrantMeStrength @hickeys @gekka @drewbatgit @PRMerger12