No release available (on GitHub)
FroggieFrog opened this issue · comments
Describe the bug
The Releases section on GitHub has no entries, but the documentation refers to this section.
Expected behavior
All releases are also available in the Releases section on GitHub.
I don't think a release would be that useful for this type of app. Probably a self-contained app would make any sense. But still: How useful would it be?
Other opinion on this?
At least fix the documentation to point to a ready-to-use zip people can download?
Lots of repos just zip up the source at a certain point and share it as a "release", which is hardly different from tags but it will show up in the sidebar of the repo homepage as a download link.
I would expect a zip file tagged with a version (like the docker image) and that zip file should contain the output from dotnet publish src/BaGetter --configuration Release --output artifacts which is used inside the workflow of release.yaml.
It should be possible to create a release from a workflow.
With this in place a user can be sure that all distributions (docker image, zip file, tagged source) are the same (I think).
I don't think a release would be that useful for this type of app. Probably a self-contained app would make any sense. But still: How useful would it be? Other opinion on this?
Just wanted to add that a release artifact in Github would be useful for some folks. One of the reasons the team I work with chose Baget initially was for the ease of deploy and not having to build the release ourselves was an appeal. Evidencing the product at discrete deployable versions was also useful for auditing purposes. I'm sure there will be folks like us who are trying to address the .NET 3.1 EOL issue and upgrade Baget to Bagetter, and release artifacts would help. I hope that makes sense. I really appreciate the work that has gone into setting up Bagetter.
@ajgbon There is already an artifact available. See the actual run aof the release workflow: https://github.com/bagetter/BaGetter/actions/workflows/release.yml
Creating a proper entry in the Releases section of GitHub seems to be a bit harder, but I still would prefer that.
@FroggieFrog - thanks for pointing that out, I hadn't spotted that. That's useful to know. I agree with your overall comment about having a Releases section with the output, but appreciate the extra work needed.
The artifacts you are seeing in the workflow are artifacts stored from the runners.
With admin privileges i can see the artifact zips in the runned actions.
I'll look into this issue how we can produce releases.
here's a sample for simple release notes creation
https://github.com/visualon/Open-Xml-PowerTools/blob/8fdb681976b85135c38f1ad445f8df59b0633e6f/.github/workflows/build.yml#L102
you can also add the packaged zip file to be uploaded to the release
Thanks @viceice for the example. I modified our actions to create a release on GH accordingly.
🎉 Its working now!