Repository navigation
Conversation
|
Warning This pull request was closed automatically. Please don't raise pull requests against an existing issue that another user has raised until it's been marked with a |
|
Thanks for submitting a PR to the GitHub Docs project! In order to review and merge PRs most efficiently, we require that all PRs grant maintainer edit access before we review them. For information on how to do this, see the documentation. |
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
The review identifies only a documentation clarification and related guidance link, with no active issues reported.
No open issues 🎉
What changed in this PR
Clarifies that setting the .github-private repository to Internal visibility is incompatible with member-only organization profiles and links to the relevant documentation.
Changes:
- Added a compatibility note for the Internal visibility option.
- Linked to member-only organization profile README guidance.
| File | Description |
|---|---|
| content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/create-github-private-repo.md | Documents the incompatibility between Internal repository visibility and member-only organization profiles, with a link to related guidance. |
Review effort: Lite
Closes #46976
What article on docs.github.com is affected?
content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/create-github-private-repo.mdWhat part(s) of the article are updated?
In the section "Creating a repository for your enterprise governance", added clarification note and link that setting repository visibility to Internal is not compatible with a member-only organization profile (which requires private visibility).