Skip to main content
Merge when the generated code is ready for deployment. The PR meets quality standards, completes required functionality, and aligns with your project guide.
Post-Code-Generation Options: Merge (this page) | Close | Refine PRChoose Merge when: The generated code meets quality standards with no critical gaps.

​
Merge Criteria

Apply this checklist to determine merge readiness:
CriteriaRequirement
Critical gapsZero
Major gaps3 or fewer (or refinement complete)
Project guide completion80% or higher
Build statusPassing
TestsPassing (if applicable)
Gap Severity Definitions:
  • Critical - Security vulnerabilities, broken core functionality, data loss risks, architectural violations
  • Major - Missing error handling, incomplete features, performance issues, inadequate testing
  • Minor - Code style inconsistencies, documentation improvements, minor optimizations

​
Decision Matrix

ConditionDecision
Zero critical gaps, minor gaps onlyMERGE
Major gaps 3 or fewer, no critical gapsREFINE
Critical gaps >0 OR fundamental issuesCLOSE

​
Review Process

1

Verify project guide completion

Check that the PR addresses requirements from your project guide:
  • Compare PR file changes against project guide requirements
  • Calculate completion: (completed items / total items) x 100
  • Verify 80% or higher completion threshold
  • Document any incomplete requirements
For detailed verification steps, see Project Guide Review.
2

Review PR documentation

Verify the PR includes:
  • Clear description of changes
  • Solution approach
  • Testing performed
  • Known limitations or follow-up work
  • Meaningful commit messages
3

Test locally

Validate the code in your local environment:
git fetch origin
git checkout [branch-name]
git pull origin [branch-name]
# Install dependencies (npm install, etc.)
# Run build
# Run tests
Verify build and tests pass without critical errors.
4

Assess code quality

Review generated code for:
  • Adherence to your codebase patterns
  • Proper error handling
  • Code style consistency
  • Integration with existing code
  • Performance considerations
5

Document gaps

Categorize any issues found:
  • Critical - blocks merge
  • Major - requires refinement if more than 3
  • Minor - acceptable
If critical gaps exist, choose Close. If major gaps exceed 3, choose Refine.

​
Merge Conflicts

Select Fix Merge Conflicts from the Blitzy PR dropdown menu to resolve conflicts automatically. Blitzy rebases your branch and regenerates any conflicting sections while preserving the original intent.

​
After Merging

Blitzy’s context updates to include the merged changes. Start your next feature request, bug fix, or backlog item immediately.

​
Projects with Submodules

Clicking Merge PR merges the parent repository only. Submodule changes are not merged automatically - merge each submodule separately in your source control tool.
Do not close or merge submodule PRs until the main repository PR is fully merged and all Refine PR cycles are complete. Doing so can break active Refine PR jobs and leave your project in a state that requires manual recovery.
The correct merge order for multi-repo projects:
1

Complete all Refine PR cycles

Finish all refinement rounds on the main repository PR. Each Refine PR job reads from submodule branches - closing them prematurely causes build failures or silent regressions.
2

Merge the main repository PR

Merge the parent repo PR through Blitzy or your source control tool.
3

Merge submodule PRs

After the main PR is merged, merge each submodule PR in your source control tool. Then update the submodule pointers in the parent repo (see Keeping Submodules Updated).

Git Submodules

Configure and manage multi-repository projects

Project Guide Review

Verify completion before merging

Refine PR

Request targeted modifications before merging

Close Pull Request

When to discard and restart