[docs] Update glossary - weekly full scan#22408
Merged
Conversation
Add Dispatch Repository safe output entry and update Integrity Filtering entry to mention blocked-users and approval-labels fields. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
pelikhan
approved these changes
Mar 23, 2026
This was referenced Mar 23, 2026
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-23
Scan Type
Terms Added
dispatch_repository): New experimental safe output type (feat: adddispatch_repositorysafe-output type for repository_dispatch events (experimental) #22315) for triggeringrepository_dispatchevents in external repositories for cross-repository orchestrationTerms Updated
blocked-users(unconditionally denies content from listed users) andapproval-labels(promotes labeled items toapprovedintegrity), both added in Add blocked-users and approval-labels to tools.github guard policy #22360Changes Analyzed
dispatch_repositorysafe-output type for repository_dispatch events (experimental) #22315 —dispatch_repositoryexperimental safe output (cross-repo repository_dispatch)blocked-usersandapproval-labelsfields intools.githubguard policypull_request_targetevent on public repositories #22378 — Runtime check disallowingpull_request_targeton public repositoriestools.github.repostotools.github.allowed-repos#22311 —tools.github.reposrenamed totools.github.allowed-reposNotes
pull_request_targetrestriction (Add runtime check to disallowpull_request_targetevent on public repositories #22378) is a security enforcement behavior, not a new configurable concept, so no new glossary term was addedallowed-reposrename (Renametools.github.repostotools.github.allowed-repos#22311) is already documented ingithub-tools.mdand the existing Integrity Filtering / Guard Policy coverage is adequateNote
🔒 Integrity filter blocked 1 item
The following item were blocked because they don't meet the GitHub integrity level.
search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter: