[TEC-521] Add instructions on re running sms checks

docs/deployment/managed-scanning/overview.md

@@ -9,10 +9,11 @@ tags:
 ---
 
 import SmsSupport from "/src/components/reference/_sms-support.mdx"
+import RerunManagedScanEmptyCommit from "/src/components/code_snippets/_rerun-managed-scan-empty-commit.mdx"
 
 # Semgrep Managed Scans
 
-Add repositories to your Semgrep organization in bulk without adding or changing your existing CI workflows through **Managed Scans**. Similar to CI workflows, Managed Scans also integrates into developer workflows through PR comments.
+Add repositories to your Semgrep organization in bulk without adding or changing your existing CI workflows through **Managed Scans**. Similar to CI workflows, Managed Scans also integrates into developer workflows through pull request (PR) or merge request (MR) comments.
 
 This is an alternative method to [adding Semgrep in CI](/deployment/add-semgrep-to-ci). Instead of adding a Semgrep job or workflow to your CI/CD pipeline, repositories are added to Semgrep AppSec Platform.
 
@@ -76,6 +77,10 @@ Semgrep Managed Scans enables you to scan multiple projects simultaneously, whic
 
 To run scans in bulk, go to the **Projects** page, select the projects of interest, and click **Scan**.
 
+## Re-run scans
+
+<RerunManagedScanEmptyCommit />
+
 ## Add a repository to Semgrep Managed Scans
 
 Learn how to add a repository to Semgrep Managed Scans:

docs/for-developers/resolve-findings-through-app.md

@@ -1,6 +1,6 @@
 ---
 slug: resolve-findings-through-app
-title: Resolve findings through the Semgrep web app
+title: Resolve findings using Semgrep AppSec Platform
 hide_title: true
 description: Sign in to Semgrep to run scans following your organization's Semgrep deployment.
 tags:
@@ -10,12 +10,12 @@ tags:
 
 import TriageStatuses from "/src/components/reference/_triage-states.mdx"
 
-# Resolve findings through the Semgrep web app
+# Resolve findings through Semgrep AppSec Platform
 
 This guide explains how you can view and triage findings in bulk through the Semgrep AppSec Platform web app.
 
 :::caution
-- Not all organizations allow developers to use the AppSec Platform; ask your security team if you have access.
+- Not all organizations allow developers to use Semgrep AppSec Platform; ask your security team if you have access.
 - When triaging through Semgrep AppSec Platform, developers typically triage findings specific to their **branch**. Avoid triaging findings in branches that are not yours to triage.
 :::
 

docs/for-developers/resolve-findings-through-comments.md

@@ -1,6 +1,6 @@
 ---
 slug: resolve-findings-through-comments
-title: Resolve findings in your pull request or merge request
+title: Resolve findings in pull request or merge request
 hide_title: true
 description: Learn to resolve or triage Semgrep findings through PR or MR comments.
 tags:
@@ -93,9 +93,9 @@ If the finding is a false positive, acceptable risk, or similar, you can choose
 ![A completed triage flow.](/img/pr-comment-triage-response.png#md-width)
 _**Figure**. A completed triage flow._
 
-### Re-run a job or workflow
+## Re-run a job or workflow
 
-After resolving or triaging the findings in your PR or MR, you must re-run the Semgrep job or workflow. See the following list for a link to your CI provider's documentation:
+Resolving or ignoring findings does not automatically re-run Semgrep checks. After resolving or triaging the findings in your PR or MR, you must re-run the Semgrep job or workflow. See the following list for a link to your CI provider's documentation:
 
 <!-- list arranged by popularity -->
 <!-- Some of these are from the release notes because they have a screenshot or indication of where the retry menu is -->
@@ -107,6 +107,7 @@ After resolving or triaging the findings in your PR or MR, you must re-run the S
 - [<i class="fas fa-external-link fa-xs"></i> Restarting or rerunning a pipeline in Jenkins](https://www.jenkins.io/doc/book/pipeline/running-pipelines/#restarting-or-rerunning-a-pipeline)
 - [<i class="fas fa-external-link fa-xs"></i> Re-run a job in CircleCI](https://circleci.com/docs/rerun-failed-tests/)
 - [<i class="fas fa-external-link fa-xs"></i> **Retry a job**](https://buildkite.com/resources/changelog/231-retry-failed-jobs-while-builds-are-running/) from the [**Dashboard > Build view**](https://buildkite.com/docs/pipelines/dashboard-walkthrough) in Buildkite.
+- [<i class="fas fa-external-link fa-xs"></i> Re-run a Semgrep Managed Scan check](/docs/kb/semgrep-appsec-platform/rerun-managed-scans)
 
 ## Appendix: triage statuses
 

docs/kb/semgrep-appsec-platform/rerun-managed-scans.md

@@ -0,0 +1,11 @@
+---
+description: How to re-run a Semgrep Managed Scan check for a pull or merge request.
+tags:
+  - Semgrep Managed Scans
+  - Troubleshooting
+---
+import RerunManagedScanEmptyCommit from "/src/components/code_snippets/_rerun-managed-scan-empty-commit.mdx"
+
+# How to re-run a Semgrep Managed Scan
+
+<RerunManagedScanEmptyCommit />

src/components/code_snippets/_rerun-managed-scan-empty-commit.mdx

@@ -0,0 +1,9 @@
+You can re-run full scans from the **Projects** page in Semgrep AppSec Platform.
+
+There is no manual "re-run" action for pull request (PR) or merge request (MR) Semgrep Managed Scans. To re-run a PR or MR scan, push a new commit to the PR or MR branch. This triggers a new scan automatically.
+
+If no code changes are needed, you can push an empty commit:
+```
+git commit --allow-empty -m "Trigger Semgrep scan"
+git push
+```

src/theme/Navbar/Content/index.tsx

@@ -153,7 +153,7 @@ export default function NavbarContent(): JSX.Element {
       className: currentSection === 'explore' ? 'navbar__link--active' : '',
       items: [
         { label: "What's Semgrep", to: '/introduction' },
-        { label: 'For developers', to: '/for-developers/overview' },
+        { label: 'For developers', to: '/for-developers/overview', activeBasePath: '/for-developers' },
         { label: 'Release notes', to: '/release-notes' },
         { label: 'Support & resources', to: '/support' },
         { type: 'html', value: '<hr style="margin: 0.3rem 0;" />' },