retain the required managed-validation status for every pull request;
use a bounded fast path for documentation and baseline-workflow-only changes;
keep the full test, lint, typecheck and build suite for runtime-affecting changes;
stop duplicate feature-branch validation where the pull-request event already covers it.
Safety
The fast path still checks whitespace errors and unresolved merge markers. If the base branch cannot be resolved safely, validation falls back to the full suite.
## Summary
- retain the required managed-validation status for every pull request;
- use a bounded fast path for documentation and baseline-workflow-only changes;
- keep the full test, lint, typecheck and build suite for runtime-affecting changes;
- stop duplicate feature-branch validation where the pull-request event already covers it.
## Safety
The fast path still checks whitespace errors and unresolved merge markers. If the base branch cannot be resolved safely, validation falls back to the full suite.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Safety
The fast path still checks whitespace errors and unresolved merge markers. If the base branch cannot be resolved safely, validation falls back to the full suite.