debian/watch: Ignoring pre-release on GittHub

[Kentaro Hayashi <kenhys@gmail.com>]

Hi,

Recently, I've faced an issue with debian/watch with pre-released version.

Here is the scenario:

1. upstream releases x.y.z with pre-release label. (tagged with x.y.z)
2. new release x.y.z was detected on developer dashboard
(https://qa.debian.org/developer.php)
3. upstream releases x.y.z as the official release. (re-tagged with x.y.z)

After step 3, it is okay to do packaging normally, but Just after step
1, there may be a possibility
to be overlooked that it should not be ready for packaging. (from
qa.d.o overview)
(even though looking at GitHub release page, it is obvious that it is
"pre-release")

Is there any good rule to ignore the pre-release in debian/watch?


-- 
Kentaro Hayashi <kenhys@gmail.com>