Repo sync for protected branch #2558
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…docs-pr into sentinel-merge
Co-authored-by: Shlomo Sagir <[email protected]>
…docs-pr into sentinel-merge
Update sharding policy examples
Doc: Fixed wrong order of sort
Merging Sentinel data to Kusto - in review with Shlomo
Publish to live, Sunday 4 AM PST, 2/23
Contributor
Author
|
Learn Build status updates of commit 8c55ed0: ✅ Validation status: passedFor more details, please refer to the build report. For any questions, please:
|
learn-build-service-prod
bot
deleted the
main638759093992269595sync_temp
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.