Skip branch updates for test-only pushes when strict=False#2319
Merged
hiroshinishio merged 2 commits intomainfrom Feb 24, 2026
Merged
Skip branch updates for test-only pushes when strict=False#2319hiroshinishio merged 2 commits intomainfrom
hiroshinishio merged 2 commits intomainfrom
Conversation
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
mainonly contains test file changes and the repo's branch protection doesn't require branches to be up-to-date (strict=False), skip updating all open GitAuto PR branchesstrict=True(like Foxquilt) still get updates as before since they require up-to-date branches before mergingget_required_status_checksto return aStatusChecksResultdataclass instead of a tuple, exposing thestrictflag from GitHub's branch protection APISocial Media Post (GitAuto)
Every merge to main triggered branch updates on all open GitAuto PRs - even when the merge was just test files. For repos that don't require up-to-date branches, that's pure CI waste. Now we check the branch protection
strictsetting and skip updates when it's safe to.Social Media Post (Wes)
Noticed every test-only merge was triggering CI reruns on all open PRs. The branch update logic didn't distinguish between code changes and test changes. Added a check: if all changed files are tests and the repo doesn't enforce up-to-date branches, skip the update. Simple filter, fewer wasted CI runs.