We should regularly "touch" this repository to force GitHub to regenerate http://gap-packages.github.io, so that newly added package repository appear, and meta data changes become visible.
A simple way to ensure that would be to setup a daily Travis cron job, which would check out the repository, and run the force-rebuild.sh script in it. Of course we'd have to add an (encrypted) authorization key into the .travis.yml file to ensure suitable push access.
We should regularly "touch" this repository to force GitHub to regenerate http://gap-packages.github.io, so that newly added package repository appear, and meta data changes become visible.
A simple way to ensure that would be to setup a daily Travis cron job, which would check out the repository, and run the
force-rebuild.shscript in it. Of course we'd have to add an (encrypted) authorization key into the.travis.ymlfile to ensure suitable push access.