organizations

Subscribe to all “organizations” posts via RSS or follow GitHub Changelog on Twitter to stay updated on everything we ship.

→ ~ cd github-changelog
→ ~/github-changelog|main git log main
showing all changes successfully

Improved innersource collaboration and enterprise fork policies

Previously, three aspects of repository forks caused friction to innersource collaboration and administration:

  1. Repositories could not be forked within a single organization.
  2. Repositories with internal visibility could not be forked to an organization.
  3. Enterprise owners lacked control over where repositories could be forked.

These obstacles have been addressed with the following new features. We’re always looking for new ways to improve repository collaboration and we welcome your ideas.

Fork a repository to the same organization as its parent

Previously, a repository could be forked only to a different organization or user account.

Now, a repository can be forked to the same organization as its parent repository, addressing situations where people are working in one organization and don’t want to fork a repository to a different organization or user account.

Fork internal repositories to enterprise organizations

Previously, when a repository with internal visibility was forked, the fork was automatically created in the person’s personal account space and its visibility was changed to private.

Now, people can fork an internal repository to an organization in the same enterprise, and the fork will retain its internal visibility. When forking an internal repository, you can choose which of the enterprise’s organizations should receive the fork – similar to forking a public repository, except that:

  1. The destination organizations will be limited to those within the enterprise of the parent repository.
  2. You will not be permitted to change the internal visibility of the fork while forking it.

Enterprise owners can limit where forks can be created

Previously, enterprise owners couldn’t restrict where repositories in the enterprise could be forked. This was important for them to keep confidential repositories from accidentally being forked to an exposed location.

Now, enterprise owners can control where enterprise members can fork repositories. Forking can be limited to preset combinations of enterprise organizations, the same organization as the parent repository, user accounts, and everywhere.

Image of enterprise settings for controlling where repositories can be forked

More information

Learn more about working with forks, or enforcing a policy for forking repositories, in the GitHub documentation.

We appreciate feedback on this and other topics in GitHub’s public feedback discussions.

See more

Organization Profile Updates: Member-only READMEs and pinned private repositories

tortenfabrik-relaode_final!-Apple ProRes 422 HQ 2022-04-20 17_18_03

Now you can customize your organization's Overview page to show content dedicated to public users or members of the organization. A new member view is only visible to members of the organization and can be controlled in the sidebar to toggle between public and member view.

A README only visible to members

Similar to the public organization README that we released last year, you can now create a README that is only visible to members of your organization. In the .github-private repository the /profile/README.md will be displayed on your organization's Overview page.

Pinned private repositories

Organization owners are able to define a set of six public, private or internal repositories that are only visible to members of their organization, enabling members to quickly access popular or frequented repositories.

For more information about the new features, see "Customizing your organization's profile".

See more

Export Organization Members

Organization owners on GitHub.com and GitHub Enterprise Cloud can now export a list of the organization's members in JSON or CSV format, through the 'Export' button on the People tab at github.com/orgs/<organization>/people.

Export organization members button

See more

READMEs for organization profiles

GitHub README

Organizations can now display a README.md on their profile Overview.

Start with creating a .github repository for the desired organization. Make sure it's public. Add a profile folder to your .github repository and add a README.md file to the profile folder.

The contents of your README.md file will appear on the Overview page of the organization, visible to everyone. For an example, see the GitHub Overview page or learn more in the documentation.

See more