You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we have to have two organizations, one for our private/public software development and another one for documentation development. This is really complicating our development cycle, and it would be nice not to have two organizations/multiple repositories for a single project.
The reason why we have to do this is that we do not want to give access to private repositories to readthedocs, I think understandably. We only want to use readthedocs for public ones. This would allow us to have a single organization and develop our projects integrated. Can this not be fine tuned based on how the organization plans to use it?
Read the Docs for Business asks for one additional permission (repo) to allow access to private repositories and to allow us to setup SSH keys to clone your private repositories. Unfortunately, this is the permission for read/write control of the repository but there isn’t a more granular permission that only allows setting up SSH keys for read access.
Describe the solution you'd like
Have readthedocs ask for the minimal amount of permissions based on the usage of the organization of the project. Not having to give access to private repositories. Give the option to the organization on how many features or permissions are enabled to readthedocs?
Alternative solutions
I have tried manually setting up web hooks so that one repo from one organization can trigger GitHub Actions and builds from the readthedocs accessed documentation.
Hi, this is due to RTD using a GitHub OAuth application, which doesn't allow selecting which projects you want to give access, the new recommended way is to create a GitHub app https://docs.github.com/en/apps/creating-github-apps/about-creating-github-apps/about-creating-github-apps. We have discussed internally about migrating our GitHub OAuth app to a GitHub app, but it requires a lot of work, so we haven't given it priority.
What's the problem this feature will solve?
Currently we have to have two organizations, one for our private/public software development and another one for documentation development. This is really complicating our development cycle, and it would be nice not to have two organizations/multiple repositories for a single project.
The reason why we have to do this is that we do not want to give access to private repositories to
readthedocs
, I think understandably. We only want to usereadthedocs
for public ones. This would allow us to have a single organization and develop our projects integrated. Can this not be fine tuned based on how the organization plans to use it?Describe the solution you'd like
Have
readthedocs
ask for the minimal amount of permissions based on the usage of the organization of the project. Not having to give access to private repositories. Give the option to the organization on how many features or permissions are enabled toreadthedocs
?Alternative solutions
I have tried manually setting up web hooks so that one repo from one organization can trigger GitHub Actions and builds from the
readthedocs
accessed documentation.Additional context
This issue
The text was updated successfully, but these errors were encountered: