Merged
Conversation
Add Enterprise API Endpoint (api-target), GH_AW_ALLOWED_DOMAINS env var, and update Lockdown Mode to reflect automatic min-integrity protection for public repositories. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Glossary Updates - 2026-03-17
Scan Type
Terms Added
api-target): Engine configuration field for GHEC/GHES deployments that auto-configures domain allowlists — added from PR Compiler: auto-add GHES domains to--allow-domainswhenengine.api-targetis set #21301GH_AW_ALLOWED_DOMAINS: System-injected env var for URL sanitization in safe output jobs, populated from network config andapi-target— added from PR Compiler: auto-add GHES domains to--allow-domainswhenengine.api-targetis set #21301Terms Updated
min-integrity: approvedis automatically applied for public repositories even without explicit lockdown configuration or custom token. Documentedlockdown: falseandmin-integrity: noneas opt-out options for workflows that process all users — from PR docs: document automatic minimum-integrity-approved guard policy for public repos #21298Changes Analyzed
--allow-domainswhenengine.api-targetis set #21301 (api-target GHES domains), Removelockdown: falsefrom all agentic workflows #21294 (remove lockdown: false), docs: document automatic minimum-integrity-approved guard policy for public repos #21298 (document auto min-integrity), Store default GitHub lockdown value as a named constant #21303 (lockdown default constant), fix: add write-sink guard policies for non-GitHub MCP servers on auto-lockdown #21342 (write-sink guard policies — internal implementation, no user-facing terms)Related Changes
--allow-domainswhenengine.api-targetis set #21301: Compiler auto-adds GHES domains to--allow-domainswhenengine.api-targetis setmin-integrity: approvedguard policy for public reposlockdown: falsefrom all agentic workflows #21294 / Store default GitHub lockdown value as a named constant #21303: Removed redundantlockdown: falsefrom internal workflows; lockdown defaults tofalseunless configured or triggered by custom tokenNotes
Write-sink guard policy (PR #21342) was evaluated but determined to be an internal implementation detail of the MCP gateway, not a user-facing configuration option that needs a glossary entry.