-
Notifications
You must be signed in to change notification settings - Fork 283
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Misleading sources of documentation #4286
Comments
Get it out, get it out! |
Is it now understood where this doc instance comes from? |
Is this the culprit? https://github.com/SciTools-docs/iris |
#2610 👀 |
Yep that looks like it might be it! |
It looks like it previously was being published by Jenkins, but no longer is. I don't have access to the control panel for this account. Could someone else in @SciTools/admins disable it, or redirect (maybe http 301 if possible) to our RTD instance? |
Agreed, it seems with the permission, you can just disable the github "Pages" option |
I do not seem to have permissions to do anything on https://github.com/SciTools-docs/iris. For reference, we have https://github.com/SciTools/scitools.org.uk/tree/master/iris/docs which is the docs for Scitools that includes links to the docs for Iris and Cartopy published via https://scitools.org.uk/. After Iris 2.4 we moved to ReadTheDocs (RTD) and will auto redirect to RTD when selecting the latest Iris. If someone has permissions for https://github.com/SciTools-docs/iris, I think we can either disable the pages or add a simple redirect like we do on the scitools.org.uk repo, see https://github.com/SciTools/scitools.org.uk/blob/master/iris/docs/stable_readthedocs/index.html - as per @jamesp suggested. Perhaps @bjlittle has permissions, or @pelson who I note was the first to commit to master before the automated travis commits. |
Done 👍 |
📚 Documentation
Where is this documentation being produced? Can we turn it off? It is out of date.
https://scitools-docs.github.io/iris/master/index.html
The text was updated successfully, but these errors were encountered: