Appearance
Commit Workflow
Automatic code quality analysis for every commit to GitHub and Bitbucket repositories. Changed files are scanned instantly and commit status is updated in real-time.
Prerequisites
Before enabling commit analysis, ensure you meet all requirements:
Requirements Check
- Repository linked with initial full scan completed
- Version Control Account configured with proper token permissions
- Network access from BrowserStack Code Quality server to your SCM
** Verify Token Permissions →**
Enabling Commit Analysis
Option 1: During Repository Linking
- Navigate to Projects → [Your Project] → Link Repository
- Select your Version Control Account from the dropdown
- Choose your repository from the auto-populated list
- Enable "Commit Analysis"
- Click Link Repository
Option 2: For Existing Repositories
- Go to Repositories → [Your Repository] → Edit
- Enable "Commit Analysis"
- Click Save
NOTE
Automatic Webhooks: If your VCA has webhook permissions, webhooks are created automatically. Otherwise, configure webhooks manually in your SCM platform.
How It Works
Automated Flow
- Developer commits changes to GitHub/Bitbucket
- Webhook triggers instant scan of changed files (delta analysis)
- Analysis completes and commit status is updated
- Results available in both SCM and BrowserStack Code Quality UI
Reviewing Commit Results
In Your SCM (GitHub/Bitbucket):
- Commit status shows pass/fail with issue count
- Click status badge for detailed BrowserStack Code Quality results
In BrowserStack Code Quality UI:
- Open Development History from repository summary
- Navigate to Commits tab
- Click commit to see detailed analysis
- Review new, fixed, and carried-over issues
Commit Status Types
| Status Badge | Meaning | Action Required |
|---|---|---|
| All Good | No new issues detected | Ready to proceed |
| Issues Fixed | Previous issues resolved (e.g., "+1 Fixed") | Positive change! |
| ️ New Issues | Quality issues introduced | Review and address |
| Scan Failed | Analysis could not complete | Use "Retry" button |
Platform Support
NOTE
Commit-level analysis is currently not supported for Azure DevOps.
Manual Configuration
If automatic webhook setup fails or you have restricted token permissions:
Manual Webhook Setup
For commit analysis, configure webhook in your SCM platform with:
- Events: Push events only
- URL:
/api/views/repositories/webhooks - Content Type:
application/json - SSL Verification: Enabled (recommended)
Troubleshooting
Common Issues and Solutions
| Problem | Quick Solution |
|---|---|
| Commits not scanned | Verify enterprise license and webhook exists |
| No commit status | Check token has commit status permissions |
| Webhook failures | Review token scopes and server accessibility |
| Missing in Development History | Ensure initial full scan is completed |
| Analysis timeouts | Check server resources and network connectivity |
| VCA connection errors | Verify token validity and permissions |
Related Workflows
- Pull Request Workflow → – Analysis before merge (all licenses)
- Gated Commit → – Local quality gates before push
- Token Permissions → – Required scopes for all providers