Can a repository be made public when using a GitHub Enterprise setup with SSO login? #181447
-
Select Topic AreaQuestion BodyWe are considering using GitHub Enterprise with SSO enabled. Is it still possible to mark a repository as public, or does SSO require all repositories to remain private/internal? If it depends on the configuration: what settings does the organization or enterprise admin need to adjust to allow public repositories? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
Yes — you can still have public repositories with GitHub Enterprise + SSO enabled. SSO only controls authentication and authorization. As long as the enterprise/organization admin has allowed the “public” visibility option, members can create or convert repositories to public — even when SSO is enforced. What needs to be configured? Enterprise settings → Policies → Repositories → Repository visibility Organization settings → Policies → Default repository settings Important: Summary If you want, I can also outline the exact step-by-step configuration path for Enterprise Cloud or Enterprise Server — both have slightly different menus. |
Beta Was this translation helpful? Give feedback.
Yes — you can still have public repositories with GitHub Enterprise + SSO enabled.
SSO does not force all repos to be private or internal. But it does depend on the organization’s visibility policy.
SSO only controls authentication and authorization.
Repository visibility is controlled by your organization-level “Repository visibility” policy, independently of SSO.
As long as the enterprise/organization admin has allowed the “public” visibility option, members can create or convert repositories to public — even when SSO is enforced.
What needs to be configured?
Enterprise settings → Policies → Repositories → Repository visibility
• Ensure “Public” is enabled as an allowed visibility type
…