Conversation
|
I don't think it fully addresses the issue. The problem is that something should keep track of avahi releases and copy them to the "download" folder to keep it in sync with the avahi repository. It can be either done via cron jobs here with some lag or in the avahi repository on "tag/release" events (but that would require messing with tokens for different repos). I'm not sure why this duplication is needed. Could you expand on what your use case is? |
It's related. In its current form the download folder exists to keep the old links working and the index isn't necessary for that (or it can be just static without any GitHub actions). Actions would be needed to keep the download folder in sync with the avahi repository but if it's never going to be updated there is no need to automate it either. Anyway let's see where #2 goes. |
Can fix #2 ?
Examples: