Missing use for the "addons-src" repository

[Vankata453]

Currently, there are 2 add-on-releated repositories for SuperTux - addons and addons-src. "Addons" contains the add-on archive files, downloaded by SuperTux, while "addons-src" contains the source files for those add-ons. For a user to update or add an add-on, they have to make their respective changes in both repositories.

"Addons-src" doesn't seem to currently have a use. If a user wants to access/modify the source files for an addon, they can download the .zip archive through the "Add-on Manager" in-game, or through the "addons" repository, and then view/extract/modify the contents of the respective archive directly.

The benefits of having 1 add-ons repository would be:

• Easier orientation for new users, who want to help with add-on maintenance, or add/modify an add-on.
• Not having to make changes or additions to add-ons in two separate repositories, but rather have everything in one place. Should help make maintenance a tiny bit easier.
• No risk of having differences between add-ons, or storing an older version of an add-on in one of the repositories.

I may also be missing something, but am still creating this issue to allow for discussions, revolving around this. Thanks!

[awcTSC8VgRr7cEJpgRN3]

I am in favor of addons-src as the changelog, and then make a snapshot-like zip from the commit of src in addons.

[Vankata453]

I am in favor of addons-src as the changelog, and then make a snapshot-like zip from the commit of src in addons.

I have thought about this, but am unsure how it could be automated.

Thinking about it again, an Actions workflow for that should work, hopefully it won't be too complicated to set up.

[awcTSC8VgRr7cEJpgRN3]

Thinking about it again, an Actions workflow for that should work, hopefully it won't be too complicated to set up.

I did a work on #17, you can check it out.