[WIP][INFRA] Run post-merge build every ten commits - #57555
Open
zhengruifeng wants to merge 4 commits into
Open
Conversation
zhengruifeng
changed the title
zhengruifeng
changed the title
zhengruifeng
marked this pull request as ready for review
July 27, 2026 08:02
zhengruifeng
changed the title
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.
What changes were proposed in this pull request?
Adds a commit-count job to the Build workflow. The post-merge build on Apache
masterruns only when the count is divisible by ten. The count job runs for every pushed branch; existing handling remains unchanged forbranch-4.x, forkmaster, and other branches.Why are the changes needed?
Running the post-merge build after every
mastercommit consumes substantial CI capacity. Running it every ten commits preserves regular validation while reducing that load.Does this PR introduce any user-facing change?
No.
How was this patch tested?
Ran
git diff --check.No unit test was run because this change modifies only GitHub Actions orchestration.
Was this patch authored or co-authored using generative AI tooling?
Generated-by: OpenAI Codex (GPT-5)