(I asked this in mtt-devel but got no reply, so I figured I'd ask here)

It looks like every time there is a PR merged, there's a new gh-pages deployment. This is generally fine, except that sometimes the deployments are not as a result of any actual documentation changes, but just changes in the timestamps of the documentation. I.e., no doc changes occurred, but the doc generator ran, it updated the timestamps, and therefore those timestamp changes were recorded as a git diff, which then resulted in another gh-pages deployment.

Can such spurious commits / deployments be avoided?