[BUG] Docs are not being built during CI check

[achieveordie]

Describe the bug

I believe that all of the current PRs only show "Expected — Waiting for status to be reported" for docs/readthedocs.org:sktime check. I don't know what is causing this but it must be recent since I remember this check passing few days ago.

To Reproduce

Expected behavior

Additional context

See #4093, #4075, #4087 etc.

Versions

[fkiraly]

Hm, this seems to be a GitHub GUI issue?

Because if you check directly on readthedocs, it looks like it gets built:
https://readthedocs.org/projects/sktime/builds/

[achieveordie]

I agree. The builts are there when we see through the provided link but GH doesn't show it. I doubt this is a sktime issue if that is the case.

[miraep8]

Yes, have also been looking into this as its blocking a PR from one of the new contributors I am working with. Curiously, if you look at checks that have run from the PR itself you see 18 (this number includes the ReadTheDocs build). But if you actually click on the detailed test summary the ReadTheDocs build disappears from the count and isn't included in the overall test run graph.

Now, perhaps this isn't surprising because the read the docs test (from what I can tell) isn't actually included in the test.yml file where we put together all the other tests (and I assume is just linked in from some other Github actions widget or add on? I am not totally sure how it works right now). One potential solution that we could try out could be to explicitly use the Github action for Read The Docs? Just wondering if something might be up with how its currently running and it might be nice to have it run through the same interface as everything else?

[fkiraly]

I've temporarily removed the requirement for the readthedocs check to pass, so merges become possible again (if everything else runs).
I think it's the reporting that's failing, readthedocs still builds, see above.

[fkiraly]

Hm, readthedocs integration of CI checks is back, just shortly after recovery of the readthedocs sktime project.
See #4237

One conjecture could be that the hijack of the sktime project happened already around January 11, and that somehow upset the integration, or it got intentionally removed.

Now that readthedocs account and the sktime readthedocs project is under control again, it seems whatever blocked the integration has been resolved, too.