New branches/tags from github not detected

[renaudjester]

Details

• Read the Docs project URL: https://readthedocs.org/projects/copernicusmarine/
• Read the Docs username (if applicable): https://readthedocs.org/profiles/nitreb/

Expected Result

I want to be able to see new branches and tags that I have on the repository (https://github.com/mercator-ocean/copernicus-marine-toolbox).

Actual Result

Right now I cannot see any of the new branches on readthedocs (more than a week or two old). I can see that the webhook sends all the necessary information with a 200 both on readthedocs (settings/intergrations) and github.
For example a push or commit to the branch pre-releases/2.0.0a4 doesn't appear anywhere when searching versions here. Clicking the button "Resync version" returns an error as a pop up: "There was an error syncing versions".

I also have a rule to trigger automatically a build when a tag is created but it doesn't trigger either.

Hope this can be taken care of soon since it prevents me for publishing any new documentation.

Have a good day!

[renaudjester]

Hi all :D

Today, the problem wasn't still fixed. But going on the admin page of the project I missclicked on a version and started the build of this old version. It seems that then the project was updated and all my branches and version were up to date (the automated build that I put in place even triggered).

So the bug is the following:

Readthedocs doesn't update project data by itself (version, branches etc).
It is problematic because for example it means that documentation building is not triggered automatically even with rules set properly.

A quick fix seems to trigger some random build (maybe some other actions would work). We reinitialised the OAuth connection to the repository, I don't know if this had an impact.
Maybe you want to plan a long term fix to avoid this IDLE state. Otherwise, I'll let you close this issue.

[stsewd]

Hi, we haven't seen any other reports about this problem. It usually means that a webhook is missing, or the webhook is sending the events to the wrong project. Re-syncing the webhook from RTD should fix the issue.