Skip to content

Conversation

@TravisEz13
Copy link
Member

@TravisEz13 TravisEz13 commented Oct 14, 2021

PR Summary

change order of try-catch-finally because the code never worked

  • I split out the arm runs during the debug work, so, we might as well take it.

PR Context

PR Checklist

@ghost ghost assigned iSazonov Oct 14, 2021
@TravisEz13 TravisEz13 changed the title use recommended style change order of try-catch-finally and split out arm runs Oct 15, 2021
@TravisEz13 TravisEz13 marked this pull request as ready for review October 15, 2021 00:53
@daxian-dbw
Copy link
Member

@TravisEz13 Can you please update the PR description with some more information about what this change is for? e.g. to enable new functionality? to fix an issue?

@TravisEz13
Copy link
Member Author

description updated

@adityapatwardhan adityapatwardhan added the CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log label Oct 15, 2021
@adityapatwardhan adityapatwardhan merged commit 1be0c92 into PowerShell:master Oct 15, 2021
@TravisEz13 TravisEz13 deleted the fix-packaging-ci branch October 15, 2021 19:21
daxian-dbw pushed a commit to daxian-dbw/PowerShell that referenced this pull request Oct 21, 2021
@ghost
Copy link

ghost commented Oct 21, 2021

🎉v7.2.0-rc.1 has been released which incorporates this pull request.:tada:

Handy links:

@ghost
Copy link

ghost commented Dec 16, 2021

🎉v7.3.0-preview.1 has been released which incorporates this pull request.:tada:

Handy links:

@TravisEz13
Copy link
Member Author

/backport to release/v7.0.11

@github-actions
Copy link
Contributor

github-actions bot commented Apr 29, 2022

Started backporting to release/v7.0.11: https://github.com/PowerShell/PowerShell/actions/runs/2242783372

GitHub
PowerShell for every system! Contribute to PowerShell/PowerShell development by creating an account on GitHub.

@github-actions
Copy link
Contributor

@TravisEz13 backporting to release/v7.0.11 failed, the patch most likely resulted in conflicts:

$ git am --3way --ignore-whitespace --keep-non-patch changes.patch

Applying: use recommended style
Using index info to reconstruct a base tree...
M	tools/ci.psm1
Falling back to patching base and 3-way merge...
Auto-merging tools/ci.psm1
CONFLICT (content): Merge conflict in tools/ci.psm1
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 use recommended style
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Error: The process '/usr/bin/git' failed with exit code 128

Please backport manually!

@TravisEz13
Copy link
Member Author

I don't think we should backport to 7.0

@adityapatwardhan
Copy link
Member

Packaging CI does not exist in CI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Backport-7.2.x-Done CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants