GitHub Enterprise administrators can now view additional details within the Consumed License CSV that can be found on Setting>Enterprise licensing tab. These CSV changes provide additional details on Visual Studio with GitHub Enterprise license status and membership roles to help you manage license usage across your Enterprise.
To learn more, read our docs on viewing your license usage.
If your GitHub organization is owned by an enterprise account, you can now innersource automation by sharing Actions only within your enterprise without publishing them publicly.
You can store the Action in an internal repository, and then configure the repository settings to allow access to workflows in other repositories:
These Actions in internal repositories can only be used by workflows defined in other private and internal repositories but cannot be used in workflows defined within any public repositories.
Learn more about Sharing Actions and workflows with your enterprise.
GitHub audit log streaming is now out of beta and generally available. Your experience using audit log streaming will not change, but we expanded the number of options you have for where you can stream your audit and Git events:
Enterprise owners can set up their stream in minutes by navigating to their enterprise account settings under the Audit log tab and configuring the collection endpoint.
Members of GitHub Enterprise Cloud organizations belonging to an enterprise account can now view a list of their enterprise owners under the organization's People tab. Whenever an organization member encounters a contact your enterprise owner prompt within GitHub Enterprise Cloud, a link will be offered to direct the user to the Enterprise permissions view.
The enterprise owners list is also now accessible via the GitHub API under the Organization object as the enterpriseOwners endpoint.
To learn more, read our docs on viewing your enterprise owners.
GitHub Enterprise Cloud users can now configure two new permissions when managing custom repository roles:
You can learn more about custom repository roles in our documentation.
GitHub Enterprise Cloud customers participating in the audit log streaming public beta may now use Google Cloud Storage when configuring a stream. This will allow tools that support Google Cloud Storage as a data source to more readily analyze the events data coming from a GitHub enterprise account. Learn more
GitHub Enterprise Server 3.3 is now generally available for all customers. There are three exciting new betas to explore, dozens of productivity enhancements and performance improvements for CI/CD.
For more information about GitHub Enterprise Server 3.3, read the blog post and release notes or download it today. Alternatively, enjoy this ten minute overview presentation.
Are you using the latest GitHub Enterprise Server version? Use the Upgrade Assistant to find the upgrade path from your current version of GitHub Enterprise Server to your desired version.
Team sync support for Okta is now generally available for GitHub Enterprise Cloud customers.
Team sync allows GitHub.com organizations to sync an identity provider's groups’ members to teams in GitHub. With this release, we are adding support for Okta as an identity provider alongside Azure Active Directory.
To use it, your organization needs Okta configured as an external identity provider at the organization level and SCIM enabled. Learn more about Okta team sync.
GitHub Enterprise Cloud administrators can now download and view the latest GitHub SOC 1, Type 2 and SOC 2, Type 2 compliance reports for 2021. These reports can be found under the Compliance settings tab of their enterprise account: https://github.com/enterprises/"your-enterprise"/settings/compliance.
For organizations, these reports can be found under the Organization Security settings tab of their organization: https://github.com/organizations/"your-org"/settings/security.
GitHub Enterprise Cloud standalone organizations paying by invoice may now update to an enterprise account via a self-service flow.
Organization owners may navigate to the organization's billing page and click "Upgrade to Enterprise Account" to begin. There are no changes to licensing agreement or payment terms. In the new enterprise account, every organization owner will be granted the enterprise owner role.
Enterprise accounts allow you to create new organizations, manage policies and users, and provide a single point to manage and view multiple organizations. Enterprise accounts also grant access to features like audit log streaming, enterprise verified domains, and enable cross-organization collaboration via internal repositories.
Learn more about upgrading to an enterprise account.
The GitHub Enterprise Server 3.3 Release Candidate is available. This release contains a broad range of features and enhancements across the platform including GitHub Actions, Security, and a host of helpful productivity improvements.
Read the blog post to discover the highlights in this release, or dive into the full GitHub Enterprise Server 3.3 release notes.
Release Candidates are a way for you to try the latest features at the earliest time, and they help us gather feedback early to ensure the release works in your environment. They should be tested on non-production environments.
Organizations using GitHub Enterprise Cloud now have more granular control over the repository access permissions they can grant to users, with custom repository roles – now available in Beta.
A custom repository role is created by an organization owner, and is available across all repositories in that organization. Each role can be given a custom name, and a description. It can be configured from a set of over 40 fine grained permissions. Once created, repository admins can assign a custom role to any user, team or outside collaborator in their repository.
Custom repository roles can be created, viewed, edited and deleted via the new Repository roles tab in Organization settings.
Custom repository roles are also fully supported in the GitHub REST APIs. The Organizations API can be used to list all custom repository roles in an organization, and the existing APIs for granting repository access to individuals and teams have been extended to support custom repository roles.
To get started with custom repository roles, read the docs.
