-
Notifications
You must be signed in to change notification settings - Fork 7.2k
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
Make tpn generation use different containers for different branches #16434
Conversation
This PR has Quantification details
Why proper sizing of changes matters
Optimal pull request sizes drive a better predictable PR flow as they strike a
What can I do to optimize my changes
How to interpret the change counts in git diff output
Was this comment helpful? 👍 :ok_hand: :thumbsdown: (Email) |
perhaps I should backport this because I don't think all the pre-reqs are marked. |
🎉 Handy links: |
🎉 Handy links: |
/backport to release/v7.0.11 |
Started backporting to release/v7.0.11: https://github.com/PowerShell/PowerShell/actions/runs/2271016397
|
@TravisEz13 an error occurred while backporting to release/v7.0.11, please check the run log for details! Validation Failed: {"resource":"PullRequest","code":"custom","message":"No commits between release/v7.0.11 and backport/pr-16434-to-release/v7.0.11"} |
/backport to release/v7.0.11 |
Started backporting to release/v7.0.11: https://github.com/PowerShell/PowerShell/actions/runs/2295801504
|
PR Summary
Make TPN generation use different containers for different branches.
PR Context
This allows generation of the TPN for older release branches without triggering a TPN update for master.
PR Checklist
.h
,.cpp
,.cs
,.ps1
and.psm1
files have the correct copyright headerWIP:
or[ WIP ]
to the beginning of the title (theWIP
bot will keep its status check atPending
while the prefix is present) and remove the prefix when the PR is ready.(which runs in a different PS Host).