scoped-sequential-prs

PR scoping prevents future merge breaks by checking for out-of-scope files and forward references, ensuring each PR contains only code belonging to its specific stage and maintaining a clean, organized codebase.

PR scoping isolates code changes by enforcing strict stage boundaries, checking for out-of-scope files and forward references to ensure each PR contains only code belonging to its specific stage and preventing cross-stage contamination.

Early PRs break due to code contamination from forward references to later stages. Running a contamination check blocks out-of-scope files before opening a PR, maintaining buildability and avoiding merge conflicts.

Yes, you can check for out-of-scope documentation by running a contamination check before opening a PR. This enforces strict scoping rules to prevent both code and documentation contamination across stages.

Strict PR scoping is specifically intended for complex refactoring tasks requiring multiple PRs. It enforces scoping rules to prevent contamination, ensuring each stage merges cleanly without breaking future builds.