Skip to content

rules: separate focused local checks from hosted validation #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
shinaoka merged 1 commit into from
Jul 17, 2026
Merged

rules: separate focused local checks from hosted validation #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions rules/common/docs-and-tests.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,27 @@
- Do not relax tolerances, skip failing coverage, or remove checks without a
clear reason.

## Local And Hosted Validation

- Ordinary local development and focused edit-test loops should use
non-release builds with incremental compilation enabled. Keep local checks
proportional to the changed surface instead of requiring every contributor
to rebuild and run the complete workspace before each pull request.
- Local pull-request preparation should run formatting and focused tests for
changed code, relevant documentation checks for documentation-only changes,
and focused CI-helper checks for CI-only changes. Unknown paths should fall
back to the conservative code-change policy.
- Hosted CI owns comprehensive workspace tests, coverage enforcement, feature
and backend matrices, documentation builds, hardware-dependent tests, and
clean builds with incremental compilation disabled.
- Use release mode locally when optimization semantics matter: benchmarks,
performance claims, release-only failures, unsafe or optimization-sensitive
behavior, or an explicit maintainer request. Release mode is not the default
for ordinary correctness-oriented edit-test loops.
- Repository-local policy may require stricter local validation for a specific
project or change class. Such overrides should explain why hosted CI alone is
insufficient for that risk.

## Benchmarks

- Use release-mode benchmarks for performance claims.
Expand Down
Loading