[CI/Build] Fix local CI guidance - #3225
Closed
Hubert-Zhu wants to merge 1 commit into
Closed
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
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.
Description
The built-in local CI skill, README, plugin manifest, and pull request template
referenced
scripts/run_ci_test.sh, but that entry point does not exist onmain.This change:
for build and service-based validation; and
No production code or GitHub Actions workflow behavior changes.
Open PR overlap check
Neither changes the local-CI skill or the stale
run_ci_test.shreferences;any merge conflict should be limited to separate lines.
Module
Type of Change
How Has This Been Tested?
Test commands:
Test results:
Checklist
./scripts/code_format.sh(not applicable; no code changed)pre-commit run --all-files(targeted branch-diff hooks were run)AI Assistance Disclosure
Codex identified the stale references, updated the contributor guidance, and
ran targeted validation. The human submitter remains responsible for reviewing
and defending the change.