Hi,
Indeed, the Github template could be improved.
Even if upstream doesn't manually tune the release tarball before
publishing it, my fear is that someone not used to Debian packaging
practices could download tarballs by browsing a project tags/releases
page, notice that it doesn't match (Github "tags" tarballs include the
commit hash in the base directory's name, so even if the contents is
100% identical, the sum is not) and think "Hey, Debian doesn't use the
tarballs found on Github, something's fishy !".
For now I use this workaround for tags:
```
Download-Url-Mangle:
s%api.github.com/repos/([^/]+/[^/]+)/git/(.*)%github.com/$1/archive/$2.tar.gz%
```
And for releases:
```
Release-Only: yes
Download-Url-Mangle:
s%api.github.com/repos/([^/]+/[^/]+)/tarball/(.*)%github.com/$1/archive/refs/tags/$2.tar.gz%
```
I also don't understand why `Uversion-Mangle: auto` isn't the default,
since `~` is Debian-specific and without it, uscan always considers
pre-releases as newer than the matching final release.
Regards,
--
Raphaël Halimi
