MicrosoftDocs
Update service-limits.md
@marche0133 : Thanks for your contribution! The author(s) have been notified to review your proposed change.
![prmerger-automator[bot] avatar](https://avatars.githubusercontent.com/u/22479449?v=4 "Published by a pub.dev verified publisher"){kind=small}
Learn Build status updates of commit 2280285:
:white_check_mark: Validation status: passed
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/communication-services/concepts/service-limits.md | :white_check_mark:Succeeded |
For more details, please refer to the build report.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
![learn-build-service-prod[bot] avatar](https://avatars.githubusercontent.com/in/237442?v=4 "Published by a pub.dev verified publisher"){kind=small}
@tophpalmer
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team
@v-dirichards @tophpalmer it has been a month. Can you take a look and get this merged in?
Hi @Court72 @tophpalmer , can you give an ETA when this can be merged? thanks
@marche0133 - This pull request was opened in the public repo. It appears you have permissions in the private repo. If you pull your commit to the private side, it can be merged along with validation processes happening.
@marche0133
Because this PR was created in the public repo, only the listed author can sign off on updates. You can wait for approval from the author @tophpalmer or you can close this PR and make the change in the private repo azure-docs-pr.
Read about authors working in the public repo for more information.
It looks like you have access to the private repo but if you need help, see Get started contributing to the Microsoft Learn platform.
Important: Contributor guidance has moved to https://learn.microsoft.com/help/ To access the guides, you must log in with your Learn profile. If you don't have a Learn profile, follow the instructions at Manage your Microsoft Learn profile settings | Microsoft Learn to create one.
After you make your changes in the private repo, review the articles on staging, and fix any validation issues, you can add the #sign-off comment to let PR reviewers know that the updates are ready to be merged.
Thanks
I sent an email to the content owner today.
@MicrosoftDocs/public-repo-pr-review-team
@tophpalmer Can you review this old PR and determine whether it needs to be closed or merged?
@MicrosoftDocs/public-repo-pr-review-team
I sent a Teams message to the content owner today.
@MicrosoftDocs/public-repo-pr-review-team
I sent a Teams message to the content owner today.
@MicrosoftDocs/public-repo-pr-review-team
I sent an email to the content owner today.
@MicrosoftDocs/public-repo-pr-review-team
Hi @v-dirichards , @tophpalmer , this has been opened for awhile - what can we do to have this merged to public doc?
Hi @v-dirichards , @tophpalmer , this has been opened for awhile - what can we do to have this merged to public doc?
@marche0133 In the public repo, pull requests should be signed off by the author, another member of the content team, or a PM. Currently the PR is hung up in the approval process. You could try opening it in the private repo (azure-docs-pr) or finding a different way to get the needed approval for this PR.
I can make the same changes to private repo and get it merged there. would that reflect on the public doc once i make changes in private repo?
I can make the same changes to private repo and get it merged there. would that reflect on the public doc once i make changes in private repo?
Yes, the change will make it to the public repo within a day or so.
Hi @v-dirichards I made the same change in private repo here: https://github.com/MicrosoftDocs/azure-docs-pr/pull/303994 can we have this merged? i will close this one if that one goes through
this can be closed as the change went through in Private repo - i will work with @marche0133 have this closed. Thank you everyone