10. Glossary

Every term below is cross-referenced to the subsection where it's covered in depth.

Assignee — A person explicitly marked as responsible for resolving an issue or pull request, distinct from a reviewer. (6.3)

Branch — A lightweight, movable pointer to a specific commit, enabling a separate line of history. (1.3.3)

Branch protection rule — A repository setting that constrains what can happen to a branch, such as requiring reviewed pull requests before merging. (7.4)

Closing keyword — A phrase (Closes #12, Fixes #12, Resolves #12) in a pull request that auto-closes the referenced issue on merge. (4.2)

Clone — Downloading a full copy of a repository, including its .git history, to a local machine. (1.3.1)

CODEOWNERS — A file mapping paths to people or teams auto-requested as reviewers on matching pull requests. (3.1)

Codespaces — A cloud-hosted development environment provisioned from a repository's dev container configuration. (5.4)

Commit — A local, timestamped snapshot of a repository's entire state, paired with a message and unique hash. (1.3.2)

Copilot Agent Mode — Copilot's autonomous mode, capable of multi-file changes and proposing terminal commands with less step-by-step prompting. (5.2)

Dev container — A repository-stored configuration (devcontainer.json) defining a consistent, reproducible development environment. (5.4)

Discussion — An open-ended GitHub conversation surface with no expectation of resolving to a single closed outcome. (4.1)

Enterprise Managed Users (EMU) — An identity model where accounts are provisioned and controlled entirely through a company's identity provider. (7.3)

Fork — A copy of a repository under your own account that stays connected to its upstream source, typically to propose changes back. (3.2, 8.6)

GitHub Actions — GitHub's automation engine, running YAML-defined workflows in response to repository events. (5.1)

GitHub Flavored Markdown (GFM) — GitHub's Markdown extensions (task lists, autolinked issues, @mentions) beyond standard Markdown. (2.3)

GitHub Flow — A lightweight, branch-per-change workflow built around keeping main always deployable. (2.2)

GitHub Pages — A GitHub feature that publishes a public static website generated from repository content. (4.4)

Gist — A shareable, individually version-controlled code snippet, not attached to any repository. (4.4)

Issue — A tracked unit of work — a bug, task, or request — expected to eventually close. (4.1)

Label — A tag applied to an issue or pull request to encode a category, such as priority or type. (6.2)

LICENSE — The file that states the legal terms under which a repository's code may be used, modified, or redistributed. (3.1, 8.1)

Main branch — A repository's default, long-lived branch, kept deployable under the GitHub Flow. (1.3.3, 2.2)

Milestone — A grouping of issues and pull requests toward a shared target, with automatically calculated completion. (6.2)

Multi-model support — Copilot's ability to use multiple AI model providers rather than a single fixed model. (5.2)

Notification — An alert generated by a subscription trigger: watching a repository, being @mentioned, assignment, or participation. (4.3)

Organization — A shared account grouping repositories, teams, and members under common billing and settings. (2.1)

Passkey — A phishing-resistant, device-bound credential capable of replacing a password entirely. (7.1)

Personal account — A GitHub account owned and controlled by one individual. (2.1)

Pull request — A proposed code change carrying a diff, driving GitHub's code review and merge workflow. (2.2, 4.1)

Repository — The tracked container holding a project's full history, files, commits, and branches. (1.3.1)

Runner — The virtual machine (GitHub-hosted or self-hosted) that executes a GitHub Actions job. (5.1)

Saved reply — A reusable canned response insertable into issue or pull request comments. (6.3)

SECURITY (file) — A file explaining how to responsibly report a security vulnerability in a repository. (3.1)

GitHub Sponsors — GitHub's built-in funding mechanism for sponsoring open-source maintainers directly. (8.1)

Team — A group of organization members used to grant repository access in bulk; teams can be nested. (7.5)

Template repository — A reusable blueprint that creates a new repository with a fresh, disconnected commit history. (3.2)

Topic — A tag a repository owner applies to improve discoverability in search. (8.6)

Two-factor authentication (2FA) — A second verification step (commonly a time-based code) added on top of a password. (7.1)

Watch — A per-repository subscription setting controlling notification volume for that repository's activity. (4.3)

Wiki — A collaborative, versioned documentation space attached to a specific repository. (4.4)

Workflow — A YAML-defined automated sequence of steps executed by GitHub Actions in response to an event. (5.1)

github.dev — A lightweight, browser-based code editor with no compute behind it. (5.5)