Resolve conflicts for #2117 #2118
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
…gement\Identity.DirectoryManagement\examples\v1.0/New-MgDirectoryRoleScopedMember.md-v1.0
…gement\Identity.DirectoryManagement\examples\v1.0/New-MgDirectoryRoleTemplate.md-v1.0
…gement\Identity.DirectoryManagement\examples\v1.0/New-MgDomainServiceConfigurationRecord.md-v1.0
…gement\Identity.DirectoryManagement\examples\v1.0/New-MgDomainVerificationDnsRecord.md-v1.0
…gement\Identity.DirectoryManagement\examples\v1.0/New-MgOrganization.md-v1.0
…gement\Identity.DirectoryManagement\examples\v1.0/New-MgSubscribedSku.md-v1.0
…gement\Identity.DirectoryManagement\examples\v1.0/Remove-MgContact.md-v1.0
…gement\Identity.DirectoryManagement\examples\v1.0/Remove-MgContract.md-v1.0
…gement\Identity.DirectoryManagement\examples\v1.0/Remove-MgDirectoryRole.md-v1.0
…gement\Identity.DirectoryManagement\examples\v1.0/Remove-MgDirectoryRoleTemplate.md-v1.0
…gement\Identity.DirectoryManagement\examples\v1.0/Remove-MgOrganization.md-v1.0
…gement\Identity.DirectoryManagement\examples\v1.0/Remove-MgOrganizationBranding.md-v1.0
…gement\Identity.DirectoryManagement\examples\v1.0/Remove-MgSubscribedSku.md-v1.0
…gement\Identity.DirectoryManagement\examples\v1.0/Set-MgOrganizationBrandingBackgroundImage.md-v1.0
…gement\Identity.DirectoryManagement\examples\v1.0/Set-MgOrganizationBrandingBannerLogo.md-v1.0
…gement\Identity.DirectoryManagement\examples\v1.0/Set-MgOrganizationBrandingLocalizationBackgroundImage.md-v1.0
…gement\Identity.DirectoryManagement\examples\v1.0/Set-MgOrganizationBrandingLocalizationBannerLogo.md-v1.0
…gement\Identity.DirectoryManagement\examples\v1.0/Set-MgOrganizationBrandingLocalizationSquareLogo.md-v1.0
…gement\Identity.DirectoryManagement\examples\v1.0/Set-MgOrganizationBrandingSquareLogo.md-v1.0
…gement\Identity.DirectoryManagement\examples\v1.0/Update-MgContact.md-v1.0
…gement\Identity.DirectoryManagement\examples\v1.0/Update-MgContract.md-v1.0
…gement\Identity.DirectoryManagement\examples\v1.0/Update-MgDirectoryRole.md-v1.0
…gement\Identity.DirectoryManagement\examples\v1.0/Update-MgDirectoryRoleTemplate.md-v1.0
…gement\Identity.DirectoryManagement\examples\v1.0/Update-MgSubscribedSku.md-v1.0
…\v1.0/Get-MgGroupAcceptedSenderByRef.md-v1.0
…\v1.0/Get-MgGroupConversationThreadPost.md-v1.0
…\v1.0/Get-MgGroupConversationThreadPostAttachment.md-v1.0
…\v1.0/Get-MgGroupConversationThreadPostInReplyToAttachment.md-v1.0
…\v1.0/Get-MgGroupMemberByRef.md-v1.0
…\v1.0/Get-MgGroupOwnerByRef.md-v1.0
…managerbyref-contains-examples-for-get-mgusermanager-and-get-mguser Prevent importing of examples not related to a commandlet
… to the hash table
…305291355 [v1] Examples Update
Update CODEOWNERS
…generator-script [V1]Examples Generator Script Review
…306020302 [v1] Examples Update
Use authorityUrl instead of tenantId when initializing MSAL
Capture current policy state so that we can make versioned changes to branch protection policies. This will enable policy history, auditing, review, standardization, and templatization. We will update policy in later PR. We can ignore the rule that states: `At least one value under RequiredStatusChecks must be specified when RequiresStrictStatusChecks is true.` or `RequiresStrictStatusChecks must be true when specifying RequiredStatusChecks.` This is getting removed. This is getting removed. * https://github.com/microsoft/GitOps.Branches/pull/73 * https://github.com/microsoft/GitOps.Branches/issues/72 This branch protection policy will not take effect until https://github.com/microsoftgraph/.github/blob/main/policies/branch-protection-sdks.yml has been removed.
Fixed non-working, autogenerated example and added a new one
…306230302 [v1] Examples Update
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Resolves conflicts for #2117. Merge was done using ours strategy.