A step-by-step walkthrough shows how to manually connect a self-hosted Forgejo repository to Read the Docs so that pushes trigger documentation builds, since Read the Docs does not natively support Forgejo yet. The trick involves deleting the existing GitHub webhook integration on Read the Docs, setting a manual repository URL, creating a fake 'GitHub incoming webhook' integration, and wiring up a matching Forgejo webhook since Forgejo's webhook payload format is compatible with GitHub's.
Table of contents
What is Read the Docs?The Read the Docs sideThe Forgejo sideThe GitHub sideConclusionQuestions this post answers
How do I trigger Read the Docs builds automatically from a self-hosted Forgejo repository?
Create a manually configured repository URL in Read the Docs project settings, then add a new integration and select 'GitHub incoming webhook' as the type even though the repo is on Forgejo, since Forgejo's webhook payload format is compatible with GitHub's. Copy the resulting webhook URL and secret into a new Forgejo webhook configured with HTTP method POST and trigger set to push events. daily.dev surfaces workarounds like this for teams wiring self-hosted git tooling into existing CI and docs pipelines.
Does Read the Docs natively support Forgejo repositories?
No, Read the Docs does not currently offer a built-in integration for repositories hosted on Forgejo, unlike GitHub which gets an automatic webhook integration. A manual workaround is required: deleting the GitHub webhook integration, setting a manually configured repository URL, and tricking Read the Docs into accepting a Forgejo webhook by choosing the GitHub integration type. developers evaluating self-hosted git platforms can track docs and CI integration gaps on daily.dev.
Share this post