Appendix B: Glossary
This glossary defines key terms used throughout this book. Terms are listed in alphabetical order. Where a term has multiple meanings in different contexts, the definition reflects its usage within GitHub administration.
Access Token — See Personal Access Token (PAT).
Actions — See GitHub Actions.
Agent Skills — Predefined or custom capabilities that extend what GitHub Copilot's coding agent can do, such as reading files, running tests, or interacting with external services through the Model Context Protocol (MCP).
API (Application Programming Interface) — A set of protocols and tools for building software integrations. GitHub provides both REST and GraphQL APIs for programmatic access to platform features.
Audit Log — A chronological record of administrative and security-relevant events within a GitHub organization or enterprise. The audit log captures actions such as permission changes, repository creation and deletion, SSO events, and policy modifications.
Audit Log Streaming — The ability to continuously export audit log events to an external destination such as Azure Event Hubs, Amazon S3, Datadog, Google Cloud Storage, or Splunk for long-term retention and SIEM integration.
Base Permission — The default repository permission level granted to all members of an organization. Can be set to none, read, write, or admin.
Branch Protection Rule — A legacy mechanism for enforcing rules on specific branches within a repository, such as requiring pull request reviews, status checks, or signed commits before merging. Largely superseded by rulesets.
Bypass List — A list of users, teams, or roles that are exempted from a ruleset or branch protection rule. Used to allow administrators or automation to perform actions that would otherwise be blocked.
CI/CD (Continuous Integration / Continuous Delivery) — A software development practice where code changes are automatically built, tested, and optionally deployed. GitHub Actions is GitHub's native CI/CD platform.
CLI (Command Line Interface) — A text-based interface for interacting with software. The GitHub CLI (gh) provides command-line access to GitHub features including repository management, pull requests, issues, and API calls.
Code Scanning — A GitHub Advanced Security feature that analyzes source code for potential security vulnerabilities and coding errors. Powered by CodeQL or third-party analysis engines.
CodeQL — GitHub's semantic code analysis engine used for code scanning. CodeQL treats code as data, allowing you to write queries that find patterns of vulnerabilities across a codebase.
Coding Agent — A GitHub Copilot capability that can autonomously perform multi-step coding tasks such as implementing features, fixing bugs, or refactoring code by creating branches, making commits, and opening pull requests.
Collaborator — A user who has been granted access to a repository that they do not own. Outside collaborators are users who are not members of the organization but have access to specific repositories.
Commit Signing — The practice of cryptographically signing Git commits to verify the identity of the commit author. GitHub supports GPG keys, SSH keys, and S/MIME certificates for commit signing.
Content Exclusion — A Copilot configuration that prevents GitHub Copilot from using specified files or repositories as context for code suggestions. Configured at the organization or enterprise level using glob-style path patterns.
Copilot Business — A GitHub Copilot subscription tier designed for organizations. Includes code completions, chat, CLI integration, and administrative controls such as policy management and content exclusions.
Copilot Chat — An AI-powered conversational interface within GitHub Copilot that can answer coding questions, explain code, generate tests, and help with debugging. Available in supported IDEs and on GitHub.com.
Copilot CLI — A GitHub Copilot feature that provides AI assistance in the terminal, helping users construct shell commands, Git commands, and GitHub CLI commands through natural language descriptions.
Copilot Enterprise — The highest tier of GitHub Copilot, adding features beyond Copilot Business such as knowledge bases built from an organization's repositories, Copilot pull request summaries, and Copilot in GitHub.com.
Copilot Individual — A GitHub Copilot subscription for individual developers. Provides code completions and chat but lacks the administrative controls and policy features available in Business and Enterprise tiers.
Custom Instructions — Organization-level or repository-level text that provides Copilot with additional context about coding standards, preferred libraries, architectural patterns, or project-specific conventions to improve the relevance of suggestions.
Custom Repository Role — A user-defined permission level that extends beyond the five default roles (read, triage, write, maintain, admin). Organizations can create custom roles that combine specific permissions for specialized workflows.
Custom Secret Scanning Pattern — A regular expression pattern defined at the repository, organization, or enterprise level that extends secret scanning to detect organization-specific secrets or credentials not covered by GitHub's built-in patterns.
Dependabot — A GitHub feature that monitors repository dependencies for known security vulnerabilities and outdated versions. Dependabot can generate alerts, open pull requests for security updates, and keep dependencies current with version updates.
Dependabot Alerts — Notifications generated when Dependabot detects a known vulnerability in a repository's dependency tree. Alerts include severity ratings and links to advisory information.
Dependabot Security Updates — Automated pull requests created by Dependabot to update vulnerable dependencies to the minimum patched version. Distinct from version updates, which target the latest version regardless of vulnerabilities.
Dependabot Version Updates — Automated pull requests created by Dependabot to keep dependencies up to date with their latest versions, independent of security vulnerabilities. Configured via a dependabot.yml file.
Dependency Graph — A representation of all dependencies declared in a repository's manifest files (such as package.json, requirements.txt, or pom.xml). The dependency graph powers Dependabot alerts and dependency review.
Dependency Review — A GitHub feature that shows the full impact of dependency changes in a pull request, including newly introduced vulnerabilities. Available as a pull request check via a GitHub Action.
Deploy Key — An SSH key that grants read-only or read-write access to a single repository. Used for automated deployments and CI/CD systems that need repository access without a user account.
EMU (Enterprise Managed Users) — A GitHub Enterprise Cloud deployment model where all user accounts are created, managed, and controlled by the enterprise's identity provider. EMU accounts are namespaced (e.g., username_shortcode) and cannot interact with resources outside the enterprise.
Enterprise Account — The top-level administrative entity in GitHub Enterprise Cloud. An enterprise account contains one or more organizations and provides centralized management of policies, billing, identity, and security settings.
Enterprise Policy — A setting configured at the enterprise level that governs behavior across all organizations within the enterprise. Enterprise policies can enforce specific configurations or delegate control to individual organizations.
Environment — A deployment target in GitHub Actions (such as production, staging, or development) that can have protection rules, secrets, and required reviewers. Environments enable controlled deployment workflows.
Fine-Grained PAT (Fine-Grained Personal Access Token) — A personal access token with granular, repository-scoped permissions. Unlike classic PATs, fine-grained PATs can be limited to specific repositories and specific permission sets, and can be required to go through an organization approval flow.
Fork — A personal copy of another user's or organization's repository. Forks allow contributors to freely experiment with changes without affecting the original project. Changes can be proposed back to the original via pull requests.
GHAS (GitHub Advanced Security) — A suite of security features available for GitHub Enterprise that includes code scanning (CodeQL), secret scanning, secret scanning push protection, and dependency review. GHAS requires a per-committer license on private and internal repositories.
GitHub Actions — GitHub's built-in CI/CD and automation platform. Actions allow you to define workflows triggered by events (such as pushes, pull requests, or schedules) that run jobs on GitHub-hosted or self-hosted runners.
GitHub App — A first-class integration mechanism for GitHub that acts as its own identity (a bot). GitHub Apps have granular permissions, can be installed on specific repositories, and use short-lived tokens. Preferred over OAuth Apps for most integrations.
GitHub CLI (gh) — The official command-line tool for GitHub. It provides terminal-based access to pull requests, issues, Actions, Copilot, and the GitHub API.
GitHub Enterprise Cloud — A cloud-hosted version of GitHub with enterprise-grade features including SAML SSO, SCIM provisioning, enterprise accounts, GHAS, audit log streaming, and enterprise-level policies.
GitHub Enterprise Server — A self-hosted version of GitHub that organizations deploy on their own infrastructure. Provides similar features to Enterprise Cloud but with full control over the hosting environment.
GitHub-Hosted Runner — A virtual machine provided and maintained by GitHub for executing GitHub Actions workflows. Available in Linux, Windows, and macOS variants with predefined software configurations.
GraphQL API — GitHub's query-based API that allows clients to request exactly the data they need in a single request. More efficient than REST for complex queries that would otherwise require multiple API calls.
IDE (Integrated Development Environment) — A software application that provides comprehensive facilities for software development. GitHub Copilot integrates with IDEs such as Visual Studio Code, JetBrains IDEs, Neovim, and Visual Studio.
IdP (Identity Provider) — An external authentication service that manages user identities and provides authentication assertions to GitHub via SAML or OIDC. Common IdPs include Microsoft Entra ID (Azure AD), Okta, PingFederate, and OneLogin.
Innersource — The practice of applying open-source development methodologies within an organization's private repositories. GitHub supports innersource through internal repository visibility, cross-organization collaboration, and discoverable repositories.
Internal Repository — A repository visibility level available in GitHub Enterprise that is accessible to all members of the enterprise but not to the public. Internal repositories are a key enabler of innersource practices.
IP Allow List — A security feature that restricts access to an organization or enterprise to requests originating from specified IP addresses or CIDR ranges.
MCP (Model Context Protocol) — An open protocol that allows AI assistants like GitHub Copilot to connect to external tools, data sources, and services. MCP enables Copilot to perform actions beyond code generation, such as querying databases, calling APIs, or interacting with project management tools.
OAuth App — A legacy integration mechanism for GitHub that authenticates on behalf of a user using OAuth 2.0. OAuth Apps have broader permissions than GitHub Apps and are generally less preferred for new integrations.
OIDC (OpenID Connect) — An identity layer built on OAuth 2.0 that provides authentication. In the GitHub context, OIDC is used for two purposes: (1) authenticating EMU users via their IdP, and (2) enabling keyless authentication from GitHub Actions to cloud providers like AWS, Azure, and GCP.
Organization — A shared account within GitHub where teams can collaborate on repositories. Organizations belong to enterprise accounts and have their own members, teams, repositories, and settings.
Outside Collaborator — A user who has access to one or more repositories in an organization but is not a member of the organization. Outside collaborators are often used for contractors or external partners.
PAT (Personal Access Token) — A token that serves as an alternative to a password for authenticating to GitHub via the API or Git operations. Available in two forms: classic (broad scopes) and fine-grained (repository-specific permissions).
Push Protection — A secret scanning feature that prevents contributors from pushing commits containing detected secrets to a repository. When a secret is detected during a push, the push is blocked and the contributor is notified with remediation options.
RBAC (Role-Based Access Control) — A security model where access permissions are assigned based on roles rather than individual users. GitHub implements RBAC through repository roles, team memberships, organization roles, and enterprise roles.
Repository — The fundamental unit of storage in GitHub, containing a project's files, revision history, issues, pull requests, and configuration. Repositories can be public, private, or internal.
Repository Ruleset — A modern mechanism for enforcing rules on branches and tags within one or more repositories. Rulesets can be created at the repository or organization level, support layered enforcement, and include bypass lists. They are the successor to branch protection rules.
REST API — GitHub's resource-based API that follows REST (Representational State Transfer) conventions. Each GitHub resource (repository, issue, pull request, etc.) has a corresponding REST endpoint.
Reusable Workflow — A GitHub Actions workflow that can be called from other workflows, enabling standardization and code reuse across repositories. Reusable workflows are defined in a repository and referenced using the uses keyword.
Runner — A machine that executes GitHub Actions workflow jobs. Runners can be GitHub-hosted (managed by GitHub) or self-hosted (managed by the organization on its own infrastructure).
Runner Group — A logical grouping of self-hosted runners that can be assigned to specific organizations or repositories within an enterprise. Runner groups control which workflows can use which runners.
SAML (Security Assertion Markup Language) — An XML-based standard for exchanging authentication and authorization data between an identity provider (IdP) and a service provider (GitHub). SAML SSO requires users to authenticate through their organization's IdP to access GitHub resources.
SCIM (System for Cross-domain Identity Management) — A standard protocol for automating user provisioning and deprovisioning between an identity provider and GitHub. SCIM ensures that when users are added to or removed from the IdP, their GitHub access is updated automatically.
Secret Scanning — A GitHub feature that detects secrets (such as API keys, tokens, and passwords) that have been accidentally committed to a repository. Secret scanning can generate alerts for repository administrators and, with push protection, prevent secrets from being pushed in the first place.
Security Advisory — A record in the GitHub Advisory Database or a repository-specific advisory that describes a security vulnerability, its severity, affected versions, and remediation steps.
Security Overview — A dashboard available at the organization and enterprise level that aggregates security findings from code scanning, secret scanning, and Dependabot across all repositories. Provides a high-level view of an organization's security posture.
Self-Hosted Runner — A machine managed by the user's organization that runs GitHub Actions workflow jobs. Self-hosted runners provide more control over the execution environment, including custom hardware, software, and network configurations.
SSH Key — A cryptographic key pair used for secure authentication to GitHub. SSH keys can authenticate Git operations and, with newer configurations, can also be used for commit signing.
SSO (Single Sign-On) — An authentication scheme that allows users to log in once with a single set of credentials and gain access to multiple applications, including GitHub. GitHub Enterprise supports SSO via SAML and OIDC.
Supply Chain Security — The practice of securing all components and dependencies that make up a software project. GitHub's supply chain security features include Dependabot, dependency graph, dependency review, and the GitHub Advisory Database.
Team — A group of organization members that can be granted access to repositories and mentioned in discussions. Teams can be nested (parent/child) and synchronized with identity provider groups.
Team Synchronization — A feature that automatically maps IdP groups to GitHub teams, ensuring that team membership stays in sync with the organization's directory. Available with SAML SSO and EMU configurations.
Two-Factor Authentication (2FA) — An additional layer of security that requires users to provide a second form of verification (such as a TOTP code or security key) in addition to their password when authenticating to GitHub.
Vulnerability Alert — See Dependabot Alerts.
Webhook — A mechanism for GitHub to send HTTP POST notifications to an external URL when specific events occur in a repository, organization, or enterprise. Webhooks enable real-time integrations with external systems.
Workflow — A configurable automated process defined in a YAML file within a GitHub repository's .github/workflows directory. Workflows consist of one or more jobs that run on triggers such as push, pull request, schedule, or manual dispatch.
Workflow Template — A predefined workflow configuration that an organization provides to its repositories as a starting point. Workflow templates appear in the Actions tab when creating new workflows and promote consistency across an organization.