The issue is that when we merge a patch that does not make any change in the documentation then the job that builds the documentation does not run and the currently working documentation is shut down.

Currently, the workaround is to run the docs job manually after we merge a non-docs-related patch.

DoD:

• The documentation job deploys the documentation correctly even after we merge non-docs-related patches.