Push to a branch, deploy to its environment
A push builds your GitHub repo, scans it with SonarQube and Dependency-Track, and deploys it to the matching environment.
What happens after git push
Branches pick the target
Each environment follows a branch, so a push to stg deploys to Staging and a push to main deploys to Production. You can also deploy by hand from the console.
Code scans on every build
SonarQube runs static analysis (SAST), and Dependency-Track checks your libraries and container (SCA).
Build logs and history
Follow the build log live, see every past deployment, and open the deployed URL from the same page.
Environment variables and domains
Sync a repository's environment variables from a dotenv file without printing the values, and add custom domains per repository. The CLI can also register your deployed login callback on the OIDC client.
Hosting, region and machine size
Choose the hosting provider, region and machine size each deployment runs on.
Connect once, then deploy with git
Link GitHub in the console, then deploy with git or the CLI. A CLI deploy shows its plan before it runs.
- git pushorigin stg
- Buildclaims-portal
- ScansSAST · SonarQubeSCA · Dependency-Track
- Stagingm4tq7.slsblx.com
Deployed to Staging, with both scan reports attached to the build.
Connect GitHub
Sign in to GitHub from the console and pick the repository. Nothing deploys until a repository is connected.
Map branches
Match each environment to its branch, such as dev to Development and main to Production.
Push or deploy
Push to the branch, or run
blocks release deploy, and read the SAST and SCA reports when the build finishes.
# See the deploy plan, then run it
blocks release deploy --dry-run --json
blocks release deploy --yes --json
# Sync env vars from a dotenv file (the plan shows key names only)
blocks release secrets sync --file .env --dry-run --json
# Read a build's scan report
blocks release reports get <buildId> --type sast --jsonIn the pipeline
- GitHub
- SonarQube
- Dependency-Track
- Kubernetes
Recent changes to Release
All Release updates- Jul 30, 20262026.07.30Blocks OS Platform
- Jan 20, 2026v3.7.10Automation, AI & Observability EnhancementsNew workflow nodes, inbound and outbound email visibility, SELISE AI, and a document management system for Storage.
- Oct 15, 2025v3.7.5Smarter Recommendations, Security & IntegrationsData-driven AI suggestions, schema-level permissions, personal access tokens, and OIDC integration.
Questions about Release
Which git providers are supported?
GitHub. You connect it once from the console, and Release builds from the repositories you choose.
What can Release deploy?
Apps from the GitHub repositories you connect. Each branch deploys to the environment it is mapped to, such as stg to Staging and main to Production.
What do the security scans cover?
SonarQube runs static analysis on your code (SAST), and Dependency-Track checks your libraries and container image for known vulnerabilities (SCA). Both reports are attached to every build.
Can I deploy without pushing?
Yes. Click Deploy in the console and pick the environment, or run blocks release deploy from the CLI.
Often used with
Start with a free project
Sign up at os.seliseblocks.com and create a project, or paste one prompt into Claude Code, Codex or Cursor and let your agent set it up through the Blocks CLI.