This site pulls info from https://github.com/decidim/decidim, but when that site's docs are updated, this repo doesn't get notified, so it can't rebuild the whole site. It seems that the site is deployed to Netlify and built directly there, and I don't think we have a way to trigger new builds except by pushing a new commit. This can be potentially problematic because docs might get updated at https://github.com/decidim/decidim but not deployed unless someone manually creates a commit in the master branch of this repo.

In order to fix this, I see three different options:

1. Manually creating empty commits to trigger rebuilds every time an update is made to the docs in `decidim/decidim. Can cause issues if someone forgets to commit.
2. Have a GitHub Actions triggering empty commits every day to force the rebuild. Can potentially cause a lot of empty, useless commits.
3. Move the build from Netlify from GitHub Actions, and rebuild the site every day. We could push changes only if they exist, for example, or push the new build every day regardless of the changes. Helps having a clean git history and is automatized, but requires some work to move the build from Netlify to here. Also requires to store things in Secrets, like the API key to push.

@andreslucena I'd go for the 3rd option, what do you think?