ci: skip heavy validation for documentation-only pull requests - #4172
Open
jackeyfaker77 wants to merge 1 commit into
Open
ci: skip heavy validation for documentation-only pull requests#4172jackeyfaker77 wants to merge 1 commit into
jackeyfaker77 wants to merge 1 commit into
Conversation
jackeyfaker77
marked this pull request as ready for review
August 29, 2026 12:00
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
Split the core CI workflow into a lightweight planning job, an optional heavy validation job, and an always-reporting required
testjob.Ordinary documentation-only changes, such as README and
docs/page updates, now skip dependency installation, build, and test work. Documentation or repository-authority files with dedicated contracts, includingLICENSE,NOTICE, and the Astryx surface inventory, continue to select the relevant heavy validation.The required
teststatus still reports successfully when heavy validation is intentionally skipped and propagates planning or heavy validation failures.Fixes #3998
Verification
heavy=false.Checklist
Does this PR entail a change in behavior?