Skip to content

Conversation

kamboj-prjwl
Copy link
Member

Description

Mandatory Checklist

  • SHOULD update ChangeLog.md file(s) appropriately
    • Update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
      • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
    • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
  • SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
  • SHOULD have proper test coverage for changes in pull request.
  • SHOULD NOT adjust version of module manually in pull request

cdxu-147 and others added 30 commits March 24, 2025 19:08
…llowing cmdlet adds a BreakingChange announcement: (#27416)

Co-authored-by: Yash <[email protected]>
…etionBeforeEndOfLife parameter (#27224)

Co-authored-by: PSCmdAssistant <[email protected]>
Co-authored-by: Yash <[email protected]>
vidai-msft and others added 19 commits May 12, 2025 12:26
…nk provider configurations (#27725)

Co-authored-by: NORTHAMERICA\tianzhu <[email protected]>
Co-authored-by: Yeming Liu <[email protected]>
Co-authored-by: Copilot <[email protected]>
@kamboj-prjwl kamboj-prjwl requested a review from isra-fel as a code owner May 13, 2025 20:26
Copy link

Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.

@kamboj-prjwl
Copy link
Member Author

/azp run

@wyunchi-ms wyunchi-ms closed this May 14, 2025
@wyunchi-ms wyunchi-ms reopened this May 14, 2025
@wyunchi-ms
Copy link
Contributor

/azp run

@wyunchi-ms
Copy link
Contributor

There are too many changes. The github cannot process this. Could you split this PR into smaller ones?

@kamboj-prjwl
Copy link
Member Author

There are too many changes. The github cannot process this. Could you split this PR into smaller ones?

Can you suggest how do process that in this case. It contains changes merged in main

@VeryEarly VeryEarly added the Do Not Squash 🚫 To prevent conflicts, this PR should not be squash merged. label May 14, 2025
Copy link

‼️ Do NOT use squash to merge this pull request. All the commits must be merged to the target branch.
‼️ Enable "Allow merge commits" in the pull request settings. Select "Merge Commits" to merge the PR. Then go back to settings and disable the option.

@VeryEarly VeryEarly merged commit 98ffd52 into Azure:release-network-2024-07-01 May 14, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Do Not Squash 🚫 To prevent conflicts, this PR should not be squash merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.