-
Notifications
You must be signed in to change notification settings - Fork 8.1k
build: fix Start-PSBuild -Output #7504
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
Conversation
Make Start-PSBuild -Output $OutDir output the build to the directory properly.
iSazonov
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Leave a comment
|
Restarted Travis-CI. |
dantraMSFT
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this needs to be thought through a little more because it's not clear to the user what -Output should contain.
anmenaga
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- PR description: to me it is not clear what is the current (bad) behavior is / what this PR is fixing. Maybe add a sentence about it or example.
- While you are at it and understand internals it would be great if you could add comments for $Output parameters of functions in build.psm1, describing expected values and behavior.
|
AppVeyor timed out. Restarted it. |
|
This PR has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed if no further activity occurs within 10 days. |
|
@kwkam Please rebase to pass CIs. |
PR Summary
Make Start-PSBuild -Output $OutDir output the build to the directory properly.
PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright headerWIP:to the beginning of the title and remove the prefix when the PR is ready.[feature]if the change is significant or affects feature tests