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.
Previously, when running a job that requires a self-hosted runner, GitHub Actions would look for self-hosted runners in the repository, organization, and enterprise, in that order.
We are changing that behavior so that the first available matching runner at any level will run the job in all cases. This allows jobs to be sent to self-hosted runners much faster, especially for organizations and enterprises with lots of self-hosted runners.
Instead of allowing all or no users to force push, admins can now be selective about who can force push to a repository.
The image below shows how in the past, admins could use a branch protection rule to allow force pushes for everyone or no one, including admins:
This all-or-nothing approach didn't support limiting force pushes to select users or teams of an admin's choosing. For example, you might have wanted to allow only a few people to force push, or you had an automated process that solely needed to force push.
Now, you can be specific about the people and teams who are allowed to force push. As shown in the image below, select Allow force pushes and Specify who can force push. Then, search for and select the people and teams who should be allowed to force push.
For more information, visit Managing a branch protection rule.