Integration & Analysis Workflows

BrowserStack Code Quality integrates seamlessly into every stage of your Software Development Life Cycle (SDLC). Whether you want to prevent bad code from being committed or automate quality checks in your master pipeline, we provide a specialized workflow for your needs.

1. Local & Pre-Commit Protection

Stop issues before they ever reach your repository. This is the most efficient way to maintain a clean codebase.

Gated Commit Workflow

Goal: Enforcement. Ensure that developers cannot commit code that doesn't meet your "Quality Gate" standards. If the scan finds critical issues, the commit is blocked locally.

• Best For: High-security projects and teams with strict "zero-regression" policies.
• 👉 Setup Gated Commits →

2. Continuous Development Workflows

Keep a pulse on your code quality as features are being built.

Commit Workflow

Goal: Visibility. Trigger a scan automatically every time a developer pushes code to a branch. This provides a "heartbeat" of quality trends and identifies issues early in the feature-building phase.

• Best For: Tracking progress on long-lived feature branches.
• 👉 Configure Commit Workflows →

3. Code Review & Merge Gates

The "Final Check" before code enters your production or main branches.

Pull Request (PR) Workflow

Goal: Automation & Feedback. Integrate directly with GitHub, GitLab, Bitbucket, or Azure DevOps. Our engine performs a delta-scan on the PR and provides inline comments and status checks directly in your SCM UI.

• Best For: Automated code reviews and ensuring only "Healthy" code is merged.
• 👉 Enable Pull Request Integration →

4. Pipeline & Remote Automation

Integrate quality checks into your existing build and release infrastructure.

CI/CD Integration

Goal: Orchestration. Plug BrowserStack Code Quality into your existing pipelines using native plugins or scripts for Jenkins, GitHub Actions, Bamboo, and more.

• Best For: Unified build and quality reporting.
• 👉 CI/CD Integration Guide →

CLI & Remote Scans

Goal: Flexibility. The Remote Scan is the engine behind all automation. Use our lightweight CLI to run scans on build servers, local machines, or custom environments where the UI is not accessible.

• Best For: Custom pipelines and air-gapped environments.
• 👉 CLI & Pipeline Script Reference →

Which Workflow is Right for You?

Feature	Gated Commit	Commit Scan	Pull Request	CI/CD
Blocks Bad Code	Yes	No	Yes	Yes
Inline PR Comments	No	No	Yes	No
History Tracking	No	Yes	Yes	Yes
Setup Effort	Medium	Low	Medium	High