Repository navigation
Conversation
… visibility is private
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues remain, and the documentation change clearly states the required private visibility and its incompatibility with internal repositories.
No open issues 🎉
What changed in this PR
This pull request clarifies that a .github-private repository must use Private visibility when it hosts a member-only organization profile README, because such READMEs do not load from internally visible repositories.
Changes:
- Added a visibility requirement to the enterprise governance repository setup instructions.
- Linked to the member-only organization profile README documentation.
- Explained the incompatibility with internal repository visibility.
| File | Description |
|---|---|
| content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/create-github-private-repo.md | Adds a note requiring Private visibility for repositories hosting member-only organization profile READMEs and links to the relevant documentation. |
Review effort: Lite
… visibility is private
Why:
Adds information that the
.github-privaterepo must haveprivatevisibility in order for organization "member only profile" to load.Closes:
#46976
What's being changed (if available, include any code snippets, screenshots, or gifs):
Updated the
content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/create-github-private-repo.mdpage to include additional note in theNOTEcall out in the "Creating a repository for your enterprise governance" section.Check off the following: