Publicamos atualizações frequentes em nossa documentação, e a tradução desta página ainda pode estar em andamento. Para obter as informações mais recentes, acesse a documentação em inglês. Se houver problemas com a tradução desta página, entre em contato conosco.

About repository visibility

You can restrict who has access to a repository by choosing a repository's visibility: public, internal, or private.

Neste artigo

Did this doc help you?

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Ou, learn how to contribute.

About repository visibility

When you create a repository, you can choose to make the repository public or private. If you're creating the repository in an organization that is owned by an enterprise account, you can also choose to make the repository internal.

Public repositories are accessible to everyone on the internet. Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members. Internal repositories are accessible to members of your enterprise account. For more information, see "About internal repositories."

Organization owners always have access to every repository created in an organization. For more information, see "Repository permission levels for an organization."

People with admin permissions for a repository can change an existing repository's visibility. For more information, see "Setting repository visibility."

About internal repositories

Note: Os repositórios internos estão disponíveis com GitHub Enterprise Cloud e GitHub Enterprise Server 2.20+. Para obter mais informações, consulte os "Produtos do GitHub".

You can use internal repositories to practice "innersource" within your enterprise account. Members of your enterprise account can collaborate using open source methodologies without sharing proprietary information publicly. For more information on innersource, see GitHub's whitepaper "An introduction to innersource."

All enterprise members have read permissions to the internal repository, but internal repositories are not visible to people outside of the enterprise account, including outside collaborators on organization repositories. For more information, see "Roles for an enterprise account" and "Repository permission levels for an organization."

Os repositórios internos são a configuração-padrão para todos os novos repositórios criados em uma organização pertencente a uma conta corporativa.

If a user is removed from an enterprise account, that user's forks of internal repositories are removed automatically.

Did this doc help you?

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Ou, learn how to contribute.