Jump to: Repository Structures | Environment | What Blitzy Needs
Repository Structures
- Single Repository
- Multi-Repository
For projects in a single repository, Blitzy clones your codebase, creates an isolated
blitzy branch, and generates code that integrates with your existing architecture.Best for: Monolithic applications, standalone services, or projects with all code in one repository.Understanding Your Environment
The more environment access you give Blitzy, the more it can validate - from basic compilation checks to full end-to-end testing with databases and external APIs.Why Environment Configuration Matters
When generating code, Blitzy compiles and tests your codebase in isolated environments before creating pull requests. This catches errors early and ensures code builds successfully.1
Source Code Only
Static analysis of your codebase
2
+ Compiler Access
Compilation checks and build validation
3
+ Runtime Access
Internal component testing with mocks/stubs
4
+ Database
Full database integration testing
5
+ API Schema & 1P/3P API Access
End-to-end workflows with all external dependencies
What Blitzy Needs
To enable runtime validation, configure:Build Instructions
Commands to install dependencies, compile, and run tests
Environment Variables
Required variables and secrets (stored securely)
Connected Repositories
Which codebases Blitzy can access and modify
Next Step
Set Up Your Project
Ready to go? Set up your first project and start generating code with Blitzy.