.github repository visibility in Enterprise Cloud organizations

[donovanmuller]

Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

https://github.com/github/docs/blob/598b5694e6afa545ecf4cb60ea309ad2f96403e3/content/actions/using-workflows/creating-starter-workflows-for-your-organization.md?plain=1#LL44C33-L44C100

What changes are you suggesting?

Following the guide to create Starter workflows for an Enterprise Cloud Organization and it mentions that the .github repository needs to be public.

For a private Organisation, it feels wrong that this repository must be public. The custom Starter workflows do not appear when the .github repository is private, so this is a prerequisite unless I'm missing something.

Additional information

No response

[welcome]

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[cmwilson21]

@donovanmuller Thanks so much for opening an issue! I'll triage this for the team to take a look 👀

[mattpollard]

👋🏻 Thanks, @donovanmuller! I can see that the article explicitly mentions that the repository must be public, and this appears in the article's GHEC version. Was there another change you were envisioning here? 👀

[donovanmuller]

@mattpollard The question is why a private Organization must have the .github repository with public visibility. This repository could contain sensitive information or references to other private/internal repositories in a private Organization. that should not be visible outside that Organization.

[mattpollard]

Thanks for clarifying 🙏🏻 Organizations themselves on GitHub don't have an associated visibility like a repository does. However, I understand that you're concerned that you must create a public repository in an organization that may not otherwise want to create public repositories 😅

As this repository, github/docs, is for contributions to GitHub Docs, I recommend that you provide your feedback about the product in the GitHub Community Discussions.

If you recommend changes to the docs, let us know! I'll close this in the meantime.

[kanoshin]

I think there is actually a mistake in the document. Here it says the following:

Starter workflows created by users can only be used to create workflows in public repositories. Organizations using GitHub Enterprise Cloud can also use starter workflows to create workflows in private repositories.

But if you try to create a private .github repository for GitHub Enterprise Cloud organization with a starter workflow, it will not be visible during Action creation. So it seems that the document mentions feature that doesn't exist.

[cmwilson21]

@kanoshin Thanks for the feedback! Since this issue is already closed, would you mind opening new issue? Then I can get it triaged and up for review. Feel free to link to any relevant information in this issue 👍