Skip to content

docs: Checkmarx One connector — branch handling + Track Scanned Branches#15358

Draft
devGregA wants to merge 1 commit into
DefectDojo:devfrom
devGregA:docs_checkmarx_branch_tracking
Draft

docs: Checkmarx One connector — branch handling + Track Scanned Branches#15358
devGregA wants to merge 1 commit into
DefectDojo:devfrom
devGregA:docs_checkmarx_branch_tracking

Conversation

@devGregA

Copy link
Copy Markdown
Contributor

What

Documents branch handling for the Checkmarx One connector in the connectors tool reference:

  • The default single-latest-scan-per-project behavior and its multi-branch blind spot (branches that weren't "latest at sync time" never import; close-old can churn findings as branches take turns winning the race).
  • The existing global Branch pin field.
  • The new opt-in Track Scanned Branches mode: latest completed scan per recently scanned branch, one engagement per branch on the mapped asset, per-branch close-old scoping, primary-branch-first deduplication ordering, branch lifecycle (stale engagements stay visible), reversibility, and the explicit note that connectors reconcile on the sync schedule — branch tracking makes syncs complete across branches, not real-time.

Pairs with the connectors service and dojo-pro PRs that implement the feature.

🤖 Generated with Claude Code

…ned Branches

Documents the default single-latest-scan-per-project behavior and its
multi-branch blind spot, the existing global Branch pin, and the new
opt-in Track Scanned Branches mode (latest completed scan per branch,
one engagement per branch, per-branch close-old scoping, primary-branch
dedupe ordering, branch lifecycle, and reversibility).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@github-actions github-actions Bot added the docs label Jul 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant