liveBook · Manning

Enterprise level

As explained in GitHub Actions in Action: Continuous integration and delivery for DevOps

The enterprise level is the configuration scope applying across organizations managed by a GitHub enterprise.

The enterprise level applies configuration across organizations managed by a GitHub enterprise. It provides centralized control over self-hosted runner availability and runner-group access. section 7.1 section 6.4

Use enterprise-level settings to:

  • Create runner groups and make them available to all organizations or selected organizations and repositories. section 7.1
  • Restrict a runner group to selected workflows, such as workflows requiring GPU-enabled runners. section 7.1
  • Disable self-hosted runner creation across all organizations, then remove existing runners manually where necessary. section 6.4

Controlled GPU runner group

Create a runner group with selected visibility, selected repository IDs, and workflow restrictions so expensive GPU runners are reserved for approved workflows rather than routine linting jobs. section 7.1

Figure 6.14 Disabling self-hosted runners at the enterprise level

Use the enterprise-level settings view to locate the control that disables self-hosted runner creation across organizations. section 6.4

How GitHub Actions in Action: Continuous integration and delivery for DevOps covers it

How deep it goes
Explains navigation, access controls, workflow restrictions, and cleanup requirements, but does not detail broader enterprise configuration.
Examples
Uses GPU-enabled runner groups, selected repositories, workflow restrictions, and enterprise settings that disable runner creation.
What it assumes
Assumes enterprise-, organization-, or repository-level administrative access and awareness of self-hosted runner security risks.
What you can do after
Operate enterprise-wide runner governance by limiting creation and routing approved workflows to controlled runner groups.
How it connects
Connects enterprise settings with organizations, repositories, self-hosted runners, runner groups, workflows, and REST API configuration.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of GitHub Actions in Action: Continuous integration and delivery for DevOps. The section links point to the parts of the book it draws on.