Issue description
Sometimes the tutorial content on https://tutorial.djangogirls.org/ falls out of sync with the content of this repo's master branch for much longer than the GitBook build and deployment should take. When that's the case, it'd be useful
- to see whether a build and deployment was triggered at all
- to see whether it went through
- if not, to see at what step it failed and how / why (e.g. by seeing the build log and deployment log)
- if the problem seems intermittent (and thus unrelated to the repo content), be able to trigger a rebuild without having to introduce a new (dummy) commit to the
master branch
Is anything of that possible?
If yes:
- For whom? (Are any special permissions / roles required on GitBook or on GitHub)?
- How? (Where would one have to look? As far as I can tell, the GitBook builds and deployments are separate from the builds done on Travis CI, so the latter can only give an indication when the build fails due mistakes in the repo content, e.g. syntax errors, and re-starting builds on Travis doesn't cause re-deployment on GitBook.)
Issue description
Sometimes the tutorial content on https://tutorial.djangogirls.org/ falls out of sync with the content of this repo's
masterbranch for much longer than the GitBook build and deployment should take. When that's the case, it'd be usefulmasterbranchIs anything of that possible?
If yes: