Update Repo Content Sync docs for GA (DOCT-2686)

[esabou-snyk]

Summary

• Release status: Updated hint from Early Access to GA (enabled by default for Enterprise plans, no opt-in required)
• New section: "Delete projects and exclude from future scans" — documents the new confirmation dialog and Exclude these projects from future scans check box, including select/clear behavior and how to reverse an exclusion
• Supported products: Added Secrets; clarified Containers as Dockerfiles only
• Terminology fixes: Docker → Dockerfile in Key capabilities and How synchronization works; "Repo Content Sync will respect" → "respects"; .Net → .NET
• Considerations section: Renamed from "Considerations for Early Access"; updated manual deactivation wording (sync does not reactivate manually deactivated Projects); added exclusion limit (100 max, silently dropped) and exclusion visibility limitation

Files changed

File	Reason
scan-fix-and-prevent/scan-with-snyk/project-repositories/snyk-repo-content-sync.md	GA release update + project deletion checkbox documentation

References

• Jira: DOCT-2686
• Source: Repo Content Sync one-pager

🤖 Generated with Claude Code

---

Note

Low Risk
Documentation-only changes with no runtime, security, or data-handling code.

Overview
Updates the Snyk Repo Content Sync page to reflect GA (enabled by default on Enterprise) instead of Early Access with Preview opt-in.

Supported environments now lists Snyk Code, Open Source, Secrets, IaC, and Containers (Dockerfiles only) and adds Secrets exclusion rules via root .snyk only. Wording is tightened throughout (Dockerfile vs generic Docker, .NET, “respects” vs “will respect”).

A new section documents Delete projects and exclude from future scans: the confirmation dialog’s Exclude these projects from future scans checkbox (default off), what happens when it’s selected vs cleared, and that re-import reverses exclusions but creates new Projects without prior history.

Considerations drops the Early Access label and expands behavior customers should know: sync won’t reactivate manual deactivations, org-wide deletion impact, 10-minute test batching, a 100-exclusion cap (API exclusion_limit_reached vs silent UI recreation), and no in-product exclusion/deletion history view.

^{Reviewed by Cursor Bugbot for commit 25271bf. Bugbot is set up for automated code reviews on this repo. Configure here.}

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[m-alony]

1. Say the check box is cleared by default — ## Delete projects and exclude from future scans
   It's not selected by default; readers will assume it is.
   ▎ …with an Exclude these projects from future scans check box. The check box is cleared by default.

2. Add two bullets — ## Considerations
   ▎ - Organization-wide deletion: Deleting a Project removes it for the entire Organization, along with its history and
   issues.
   ▎ - Test batching: Snyk batches repeated changes to the same repository and branch into 10-minute windows rather
   than testing on every commit. A change may not appear immediately.

3. add Secrets exclusions in ## How synchronization works
   ▎ - Snyk Secrets: Use a .snyk file in the root of your repository, with the global or secrets exclude sections. Snyk Secrets
   reads the root file only and does not apply .snyk files in subdirectories. For details, visit Secrets scanning in the SCM
   (https://docs.snyk.io/developer-tools/integrations/scm-integrations/secrets-scanning-in-the-scm).

[m-alony]

rephrase: Repo Content Sync deletion engine utilizes the exclusion list. When selecting the "Exclude these projects from future scans" - Snyk deletes the project and adds an exclusion to exclude the project from future scans. When the exclusion list reaches 100, the consistent deletion fails and the project will appear in the next triggered repo sync.
When deleting project using the bulk deletion - the API returns a meta.failed message with a reason of reason: exclusion_limit_reached.
When deleting a project via the UI - the consistent deletion will fail silently.

[mihaisau-snyk]

Updated

[mihaisau-snyk]

Thanks for the review, Moran — planned updates for these three points:

1. Adding "The check box is cleared by default." right after the confirmation dialog sentence in Delete projects and exclude from future scans.
2. Adding two bullets to Considerations: "Organization-wide deletion" and "Test batching" (wording tightened slightly for style consistency).
3. Adding a Snyk Secrets bullet to the exclusions list in How synchronization works, linking to the SCM secrets-scanning doc.