Would I be correct in thinking that I could zip up a subdirectory with all the files for the executable into a Release?

[rfalanga]

Select Topic Area

Question

Body

I didn't see a category for Releases, so I hope this is OK my using the Repositories category.

I've been looking into releases with GitHub. I've not used it much, so I went to the GitHub documentation and read about it. Then I selected one of my repos and created a release for it. I see that it created both a .zip file of the source and a .tar.gz of the source, which is good. However, I suspect that my colleagues at work would like me to take a deployment of something, like a website previously created by a GitHub Action, and zip that up to add it to the release. I could create a draft release then add the deployed executable and all its files and folders to it. I'd like to know if that is what people would do, if they were trying to add the deployment to a release?

[belugaman9981]

Short answer: yes, that is exactly what people do, and there’s a cleaner, more scalable way to do it than manual uploads.

[Rod-at-DOH]

Is the way suggested by rfalanga, the cleaner, scalable way of doing it?

[belugaman9981]

yes can

[N0Algorithm]

Yes. It's a standard practice to compress a built or deployed subdirectory (either from a GitHub Action or a local build) and then to upload it as a release asset. That's precisely the method that people use to share executables or website deployments via GitHub Releases.

[belugaman9981]

i know right