-
-
Notifications
You must be signed in to change notification settings - Fork 14
GitHub auto-updater #27
Comments
Check out: jman294@ed350dd This github auto updater is not tested, but a start on the idea. I did not know fully what to replace and where to place the downloaded tarballs. I have not ran the code yet, so it probably has a few bugs. Just looking to see if this is what you were envisioning. |
The idea is to use the files on the release page, but not from the repository itself, for the files inside a repository, current git auto-update can handle it ;) |
This downloads the tarballs for the needed versions. jman294@a480c15 |
We need to fetch the manually uploaded artifacts, not the tarball, all the files in the tarball can be fetched by current git auto-updater already 😃 |
I may not be the most qualified for this issue, but I'll keep working at it anyway if you want me to. :). Is this what needs to happen?
What do you mean by 'download the tarball of the needed versions'? If you think someone else is better suited to this issue than I am, I am happy to step aside :) |
At any rate, here is what I've got: |
@jman294 I'm fine if you'd like to try. The tarball means the The concept is to fetch the list of uploaded files in the release page, use |
In most recent commit I made it download needed files from the releases from github. I did not download the tarballs, only the singular needed files. In preliminary testing, it seems to work, at least from what I understand. |
Cool, would you please remove |
I believe you can squash the commits while merging. Otherwise, I can squash my commits into one. |
I prefer to see your squash first ;) |
Hi, is there possibly anything I can do to improve my pr and obtain the bounty? |
Hi @jman294, I'll test it ASAP, sorry for your waiting. |
The current general purpose git auto-updater can fetch every file inside tagged commit of any public git repository but it can't handle the manually upload assets on GitHub release page, so let's add a GitHub auto-updater for those libraries publish assets on the release page on GitHub, we can use GitHub api for the tags/versions check, and just download the files of the needed versions.
The text was updated successfully, but these errors were encountered: