Skip to main content
This guide walks you through setting up your environment and creating a new Blitzy project, from initial account provisioning through to project creation on the platform.
Jump to: Account Provisioning | Repository Structure | Branch Configuration | Source Control Integration | Codebase Context | Project Creation
Before beginning, ensure you have:
  • Administrative access - to your source control organization (required to install the Blitzy integration)
  • Team member list - for account provisioning
  • Target repositories - identified
  • Build documentation - ready

​
Phase 1: Account Provisioning

Submit a list of email addresses for all users requiring platform access to your Blitzy technical contact. When submitting the list, categorize users by their required role level:
  • Users - Standard user access for code generation workflows
  • Admins - Project and workflow management capabilities
  • Super Admins - Platform configuration and organizational settings
Account creation is handled by Blitzy. Users receive email invitations upon completion of the provisioning process. Role Permissions: For detailed specifications on capabilities and restrictions for each role type, refer to the Teams & Role Configuration guide.

​
Phase 2: Repository Structure Configuration

If you are onboarding a single repository, no additional configuration is required for this phase. Proceed directly to Phase 3: Branch Configuration.

​
Phase 3: Branch Configuration

Create a dedicated branch for Blitzy operations from your target base branch (typically main or dev):

​
Rationale for Branch Isolation

Blitzy requires a stable reference point during code ingestion. Using an inactive branch prevents synchronization issues caused by frequent commits to active development branches. This isolation ensures that the AI has a consistent view of your codebase during analysis and generation.

​
Blitzy Workflow

The isolated branch workflow follows this pattern:
1

Ingestion

Blitzy ingests code from the blitzy branch to build its understanding of your codebase
2

Generation

Generated code and modifications are committed to the blitzy branch
3

Review

Changes are reviewed via standard pull request process
4

Integration

Approved changes are merged to active branches (dev, main) through your existing CI/CD pipeline
Do not push changes to the blitzy branch while code generation is in progress. Pushing commits during generation causes conflicts, lost work, or broken builds. Wait until generation completes and the pull request is delivered before pushing any changes to the branch.
This isolation ensures generated code undergoes your existing review and CI/CD processes before integration into production code. All generated code is subject to the same quality gates, automated testing, and human review as manually written code.

​
Phase 4: Source Control Integration

Connect your source control provider to enable repository access for the Blitzy platform.
For organization-owned repositories, a workspace or organization admin may need to authorize the Blitzy integration before individual users can connect their accounts.

​
OAuth Connection

1

Log In

Log into the Blitzy platform
2

Navigate to Integrations

Go to Settings > Integrations
3

Connect Provider

Select your source control provider and follow the OAuth flow
4

Grant Access

Grant repository access permissions (see below)

​
Repository Access Configuration

Grant Blitzy access to all repositories that will be ingested onto the platform, including submodule and shared-library repositories. When in doubt, grant access to all repositories. For additional information on configuring environment-specific access and credentials, refer to the Environment Configuration guide.

​
Phase 5: Codebase Context Configuration

​
Environment Setup

Create a Blitzy environment configuration containing the information necessary to build and run your codebase. This enables Blitzy to understand your development environment and generate code that integrates with your existing build processes.

​
Build Instructions

Provide complete build and runtime setup steps that a developer would need to get your project running locally:
  • Dependency installation commands - e.g., npm ci, mvn clean install, pip install -r requirements.txt
  • Build tool invocations - required flags and configuration
  • Pre-build script execution - any setup scripts that must run first
  • Compilation steps - build order for multi-module projects
  • Local development server - startup commands
See the Environment Configuration Guide for detailed examples.

​
Secrets and Environment Variables

Document all required configuration values: API keys, PATs for private registries, service endpoints, feature flags, and authentication credentials. Use placeholder syntax with curly braces (e.g., ${DATABASE_PASSWORD}, ${API_KEY}) to reference secrets in your build instructions. Actual credential values are encrypted and stored separately. See the Environment Configuration Guide for complete details on variables vs. secrets, encryption, and configuration best practices.

​
Ingestion Prompt (Optional)

The ingestion prompt provides architectural and domain-specific context beyond what can be derived from code analysis alone. While optional, providing this information significantly improves code generation accuracy and quality.

​
Recommended Content

“Services follow a three-tier architecture: Controllers handle HTTP, Services contain business logic, Repositories manage data access”

​
Phase 6: Project Creation

With your environment fully configured, create your project on the Blitzy platform.
1

Open Workspace

Navigate to your Workspace (homepage)
2

Create Project

Click Create new project
3

Select Project Type

Choose between New Product or Existing Product based on your use case

New Product

Starting from scratch. Skip ingestion and go straight to writing a generation prompt.

Existing Product

Working with an existing codebase. Blitzy ingests your repository before code generation begins.

​
Technical Support

Contact your assigned Blitzy AI Solutions Consultant for configuration validation or troubleshooting during project setup.