PR Build Artifacts

[ThomasNieto]

Summary of the new feature / enhancement

As a user I want to be able to download binaries from the GitHub action page without having to clone the repo locally and building manually so that I can test new changes. Related #519

Proposed technical implementation details (optional)

No response

[SteveL-MSFT]

I think if someone from the community is willing to learn how to do it from the GitHub docs and submit a PR to enable it, I would certainly consider it.

[Gijsreyn]

@SteveL-MSFT It shouldn't be a challenging job to do this, and quite frankly, I already gave it a try. However, I'm wondering how you're creating current assets, because locally it didn't work as I would have expected. Could you perhaps share how you currently create the assets with the switches in the .build.ps1 file before rewriting the whole thing?

[SteveL-MSFT]

build.ps1 builds for the current platform you're running it on. In CI, we run it separately for Windows, Linux, macOS and the architectures. Each one will produce binaries in the bin folder. During release, build.ps1 has separate switches for creating msix, msixbundle, zip, tgz, etc... which is not used in CI. The output of build.ps1 tells you exactly where the resulting binaries are copied to (including manifests, ps1, etc...)