You can try to take a look at the GitHub API, e.g. [1].
Inside is an `prerelease` entry. Not sure how easy this is to
implement in uscan though.
Cheers,
Stephan
[1]: https://api.github.com/repos/lutris/lutris/releases?per_page=100
2022年12月5日(月) 16:41 Stephan Lachnit <stephanlachnit@debian.org>:
You can try to take a look at the GitHub API, e.g. [1].
Inside is an `prerelease` entry. Not sure how easy this is to
implement in uscan though.
Cheers,
Stephan
[1]: https://api.github.com/repos/lutris/lutris/releases?per_page=100
Thanks,
Instead of writing complicated rules,
it may be better to support such an API in uscan internals.
On 2022-12-08 12:59, Kentaro Hayashi wrote:0
2022年12月5日(月) 16:41 Stephan Lachnit <stephanlachnit@debian.org>:
You can try to take a look at the GitHub API, e.g. [1].
Inside is an `prerelease` entry. Not sure how easy this is to
implement in uscan though.
Cheers,
Stephan
[1]: https://api.github.com/repos/lutris/lutris/releases?per_page=10
Thanks,
Instead of writing complicated rules,
it may be better to support such an API in uscan internals.
I believe redirectors are more appropriate for that. Internals of uscan
are relatively uncomplicated and do not know any site-specific APIs.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 546 |
Nodes: | 16 (2 / 14) |
Uptime: | 148:53:27 |
Calls: | 10,383 |
Calls today: | 8 |
Files: | 14,054 |
D/L today: |
2 files (1,861K bytes) |
Messages: | 6,417,761 |