[docs] Update glossary - daily scan#38092
Merged
Merged
Conversation
Added Hide Older Comments (hide-older-comments) entry covering the new object form with match field for multi-workflow comment minimization (introduced in #37977). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
github-actions
Bot
added
documentation
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
1 participant
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.
Summary
Documentation-only update that adds a new glossary entry for the
hide-older-commentsoption.What changed and why
docs/src/content/docs/reference/glossary.mdhide-older-comments, covering:matchkey used for multi-workflow comment cleanup.No code, configuration, or schema files were modified.
Impact assessment
Testing
No automated testing required; documentation prose change only.
Verify by previewing the glossary page and confirming the
hide-older-commentsentry renders correctly with both form descriptions and the Safe Outputs Reference link.