Conversation
|
Docs are built and served via readthedocs.org, I don't know who has access. Probably @AntonOsika or @ATheorell. Build logs can be seen here: https://readthedocs.org/projects/gpt-engineer/builds/ A few weeks ago I updated a similar site built with readthedocs (which has recently updated their config format) and fixed it in this commit: ActivityWatch/docs@2c0ae72 Looks like a similar change might be needed here. |
|
Hi @ErikBjare, Thanks for sharing the link. As far as I understand, docs/conf.py had an issue that is now fixed in this PR.
Link: https://readthedocs.org/projects/gpt-engineer/builds/23192321/ Based on this, I think that once we trigger the build, it should now run successfully. I am now able to build the docs locally without any issue. |
|
It's correct that you fixed that issue, This PR can be merged though, |
|
It did fix that particular issue, but more popped up. I might do the poetry fix I suggested earlier straight away. |
|
I finished the job in #987, now builds successfully! Thanks @kristiankyvik ❤️ |

This commit seems to have broken the build pipeline for the docs. The builds have been failing for the last 6 weeks.
I have tested my changes locally, and I can successfully build the docs. This PR should fix this issue. I also added the docs/core folder to the .gitignore as I noticed it was generated when building the documentation locally.
I am not entirely about how the docs are being built and deployed - is this done automatically? If so, how?
Thanks!