FPGA programmers out there?

[nullobject]

Rygar has finally been finished, enjoy!

https://github.com/MiSTer-devel/Arcade-Rygar_MiSTer

[LFT]

Bravo!!!

[NML32]

Rygar has finally been finished, enjoy!

https://github.com/MiSTer-devel/Arcade-Rygar_MiSTer

Fantastic!!!
Thank you

[Sorgelig]

I just wanted to throw out a couple of ideas for improving the MiSTer updater script.

Is there any reason we don't leverage the GitHub releases feature?

I come from the software engineering world, and keeping binary files in a git repo isn't considered best practice because git can't do any optimisation on the changes to binary files. They are stored verbatim in the repo (i.e. every time you update a binary file, git will store another copy of it). Eventually your repo grows in size (aka. bloat).

If we use GitHub releases, then we store the compiled cores outside the repo. You can also do other neat things with the GitHub API, like only request the latest release, etc. This would make it quite trivial to add a feature to the MiSTer updater script to download the latest version of a core from the GitHub releases.

Thoughts?

This was already discussed several times. As a supporter for more than hundred repos i can say, current way is much more convenient from development point of view. More detailed i've answered on github.
There only more convenient point is to use github API to fetch the latest release. But it's just a matter of script code which is already working. The same format for release is used in Main to show the release date in OSD. So many things are bound together already. Github release feature is foreigner here.