Why release with tgz instead of putting them in gh-pages branch?

[RafalSkolasinski]

Just a generic question. When reading through https://helm.sh/docs/topics/chart_repository/ documentation I initially had the feeling that using github pages to publish chart would consist of hosting index.yaml + .tgz files just in gh-pages branch.

A manual test showed that this works properly as expected. I have then started looking at chart-releaser-action and I realized that for every chart it is creating a release with the .tgz file.

This raises few questions for me:

• What are the benefits of having the .tgz files with compressed charts as release artifacts?
• What would be cons of just putting the .tgz into gh-pages branch and hosting from there?
• Is the second option even possible with the chart-releaser?

[ghost]

I'm new to this action and repo but I'll way in on why I might do it this way:

• Github already has an artifact mechanism and if you come across the repo instead of the page you can still get access to the tar file.
• Storing archived files in version control usually isn't recommended. Imagine a page with hundreds of charts. A full clone might take a really long time and be pointless because you don't care about the archives just the source.