GitHub Enterprise Cloud customers participating in the audit log streaming public beta may now use an AWS S3 endpoint when configuring a stream. This will allow tools that support S3 as a data source to more readily analyze the events data coming from a GitHub enterprise account. Learn more
In GitHub Docs, you can choose Enterprise Cloud from the "Version" drop-down to see content that aligns with the experience of using GitHub Enterprise Cloud.
Learn how to manage your enterprise account in the new GitHub Enterprise Cloud version of our "Enterprise administrators" documentation.
GitHub Enterprise Cloud enterprise owners may now invite GitHub organizations to join their enterprise account or remove existing enterprise-owned organizations. New invitations will require organization owner approval and a final confirmation from an enterprise owner.
Learn more about self-service organization transfers.
Enterprise managed users (EMU), which allows for centralized user account administration, is generally available for customers using GitHub Enterprise Cloud (GHEC).
For more details on EMU, check out our blog post.
GitHub Enterprise Cloud's Services Continuity and Incident Management Plan is now available for self-service alongside additional resources under the Compliance tab. Enterprise owners may download and view current GitHub compliance reports from the Compliance tab of their enterprise account: https://github.com/enterprises/"your-enterprise"/settings/compliance.
Enterprise plan organization owners may view the reports from the Organization security settings tab of their organization: https://github.com/organizations/"your-org"/settings/security.
GitHub Enterprise Server 3.2 is now generally available for all customers. This release contains more than 70 new features and changes that create a more delightful development experience, and provide new security capabilities to our customers.
For more information about GitHub Enterprise Server 3.2, read the blog post and release notes or download it today.
GitHub Enterprise Cloud customers with an enterprise account may now participate in the audit log streaming public beta. This will allow you to stream audit log and Git events for your enterprise to Splunk or Azure Event Hubs. Please see the GitHub blog for more information.
The GitHub Enterprise Server 3.2 Release Candidate is available. This release includes more than 70 new features and changes to improve the developer experience and deliver new security capabilities for our customers.
Read the blog to discover the highlights in this release. Or, dive into the full GitHub Enterprise Server 3.2 release notes, and download it today.
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.
We now show a confirmation dialog when a review is requested from a team with more than 100 members, allowing users to exclude such large teams from their review request. This change makes it less likely that large teams will be added by accident, preventing unnecessary notifications for large team members.
If your organization uses IP allow lists to restrict access, any API requests made with an installation access token for a GitHub App installed on your organization already respects those settings.
GitHub is extending this so that the API request to create the installation access token will also respect your organization's allowed IP addresses.
GitHub Enterprise Server 3.1 is now generally available for all customers. It helps customers work with large, busy repositories, while enabling developers to develop and deploy with less effort than ever.
For more information about GitHub Enterprise Server 3.1, read the GitHub Enterprise Server 3.1 blog post and release notes or download it today.
GitHub Enterprise Cloud customers will now be able to approve domains for email notification routing that they are not able to verify. Enterprise and organization owners will be able to approve domains so that they may immediately augment their email notification restriction policy, allowing notifications to collaborators, consultants, acquisitions or other partners.
This capability, along with the generally available feature enterprise verified domains, will ship to GitHub Enterprise Server 3.2.
Learn more about restricting email notifications to an approved domain
GitHub Enterprise Cloud self-service compliance reports have moved to the compliance tab. Enterprise owners may download and view current GitHub compliance reports from the Compliance tab of their enterprise account: https://github.com/enterprises/"your-enterprise"/settings/compliance.
Enterprise plan organization owners may continue to view the reports from the Organization security settings tab of their organization: https://github.com/organizations/"your-org"/settings/security.
GitHub Enterprise Server 3.1 is available now as a release candidate.
The latest version of GitHub Enterprise Server brings a host of features to help teams focus on the work that matters most. That includes:
- GitHub Actions workflow visualizations – track and troubleshoot complex workflows at a glance
- Automerge pull requests – automatically merge a pull request the moment it’s ready
- Repository performance optimization – for large, busy repositories
Customers using GitHub Advanced Security will now benefit from the general availability of secret scanning, and support for more libraries and frameworks with code scanning than ever before.
For more information, see the full GitHub Enterprise Server 3.1 RC blog post.