Repository navigation
require-file-change: support regex and status filters - #13
Merged
Merged
Conversation
This was referenced Oct 22, 2026
prestist
force-pushed
the
release-note-path-regex
branch
from
October 22, 2026 13:25
c7f09eb to
d884f08
Compare
Assisted-by: AI tooling
prestist
force-pushed
the
release-note-path-regex
branch
from
October 28, 2026 13:46
d884f08 to
56eeec2
Compare
4 tasks
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.
This teaches
require-file-changeto match a path pattern and, when needed, only accept newly added files. It also switches to the paginated PR-files API and adds coverage for matching, labels, pagination, and input safety.This is the first piece of the release-note fragment rollout. It enables coreos/ignition#2347 and needs to land before coreos/repo-templates#379 turns on the new check.