[release/v7.6.2] Remove unused step to clone Internal-PowerShellTeam-Tools repo in PMC publish pipeline#27496
Merged
SeeminglyScience merged 1 commit intoMay 22, 2026
Conversation
…n PMC publish pipeline (PowerShell#27495)
SeeminglyScience
added
the
CL-BuildPackaging
adityapatwardhan
approved these changes
May 22, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Backport of #27495 to release/v7.6.2
Triggered by @SeeminglyScience on behalf of @anamnavi
Original CL Label: CL-BuildPackaging
/cc @PowerShell/powershell-maintainers
Impact
REQUIRED: Choose either Tooling Impact or Customer Impact (or both). At least one checkbox must be selected.
Tooling Impact
Removes an unnecessary step in the PMC publish pipeline template that cloned the Internal-PowerShellTeam-Tools repository.
Customer Impact
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
Cherry-pick completed cleanly with no conflicts; CI on the backport PR will validate the release pipeline template behavior.
Risk
REQUIRED: Check exactly one box.
This changes release pipeline infrastructure behavior, which can have broad operational impact despite a narrowly scoped change.