-
Notifications
You must be signed in to change notification settings - Fork 967
Repo sync for protected branch #4954
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
Conversation
Learn Build status updates of commit 8a13238: ✅ Validation status: passedFor more details, please refer to the build report. For any questions, please:
|
PRMerger Results
|
@learn-build-service-prod[bot] : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
@learn-build-service-prod[bot] : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
#label:"aq-pr-triaged" |
@TylerMSFT - can you take a stab at resolving the merge conflict here? |
Learn Build status updates of commit b794912: ✅ Validation status: passedFor more details, please refer to the build report. For any questions, please:
|
@Jak-MS - I fixed the conflict. |
[like] Jak Koke (AQUENT LLC) reacted to your message:
…________________________________
From: Tyler Whitney ***@***.***>
Sent: Friday, March 1, 2024 9:42:06 PM
To: MicrosoftDocs/cpp-docs ***@***.***>
Cc: Jak Koke (AQUENT LLC) ***@***.***>; Mention ***@***.***>
Subject: Re: [MicrosoftDocs/cpp-docs] Repo sync for protected branch (PR #4954)
@Jak-MS<https://github.com/Jak-MS> - I fixed the conflict.
—
Reply to this email directly, view it on GitHub<#4954 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKLI3VABUKL3NU3FT2FS3YLYWDY25AVCNFSM6AAAAABDVOJA3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZTHE3DGNJTHE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Learn Build Service tried pushing to main, but failed due to branch protection rule in this branch. We create this pull request for manual merge. Please merge this pull request to complete this sync.
If you want to make push successfully without creating such pull requests in future, please follow working with branch protection rule to update your branch protection rule.