Would I be correct in thinking that I could zip up a subdirectory with all the files for the executable into a Release? #183578
-
Select Topic AreaQuestion BodyI 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? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
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.