ci: enforce clean per-commit SP11 source deltas - #49
Merged
ooaklee merged 1 commit intoSep 3, 2026
Merged
Conversation
Keep the existing beta-wide integration report so historical findings remain visible, but derive the current beta tip and real topic head from the pull-request checkout's synthetic merge. Review each new topic commit independently and reject any new source-level checkpatch error, warning, or check. Require topic heads to descend from the current beta tip and reject merge commits in the topic range. This makes the reviewed delta exact and forces a relift after beta advances. Signed-off-by: Leon Silcott <leon@boasi.io>
ooaklee
marked this pull request as ready for review
September 3, 2026 12:01
This was referenced Sep 3, 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.
Summary
Strengthen the SP11 beta validator without hiding the existing beta-wide checkpatch debt. On pull-request runs, the script derives the current beta tip and real topic head from the checked-out synthetic merge, requires a current linear topic, and runs strict checkpatch on each source-changing commit independently. Any new source
ERROR,WARNING, orCHECKfails the job.Why per commit
The aggregate check remains useful for the complete integration delta, but it collapses intentional commit boundaries. That can create synthetic findings such as a binding-and-driver warning even when those changes are correctly split across patches. Kernel submissions are reviewed as patches, so the new gate evaluates each real topic commit while retaining the aggregate report for historical findings.
Guardrails
checkpatch.pl --stricton every source-changing commit and reject all three finding severities;Validation
bash -n: passgit diff --check: passTwo independent read-only OpenCode reviews found no gate-bypass defect. The second review specifically approved synthetic-merge parent ordering, Bash behavior, ancestry direction, and linearity enforcement. The workflow already checks out 256 commits, covering every current topic range.
This PR changes CI only and requires no hardware qualification.