Update index.md make sure file `SAST.gitlab-ci.yml` correct location

What does this MR do?

Related issues

Author's checklist (required)

• Follow the Documentation Guidelines and Style Guide.
• If you have developer access or higher (for example, GitLab team members or Core Team members)
  • Apply the documentation label, plus:
    • The corresponding DevOps stage and group label, if applicable.
    • development guidelines when changing docs under doc/development/*, CONTRIBUTING.md, or README.md.
    • development guidelines and Documentation guidelines when changing docs under development/documentation/*.
    • development guidelines and Description templates (.gitlab/*) when creating/updating issue and MR description templates.
  • Assign the designated Technical Writer.

Do not add the feature, frontend, backend, ~"bug", or database labels if you are only updating documentation. These labels will cause the MR to be added to code verification QA issues.

When applicable:

• Update the permissions table.
• Link docs to and from the higher-level index page, plus other related docs where helpful.
• Add GitLab's version history note(s).
• Add the product tier badge.
• Add/update the feature flag section.
• If you're changing document headings, search doc/*, app/views/*, and ee/app/views/* for old headings replacing with the new ones to avoid broken anchors.

Review checklist

All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.

1. Primary Reviewer

• Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.

2. Technical Writer

• Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.
  • Ensure Technical Writing, documentation, and a docs:: scoped label are added.
  • Add docs-only when the only files changed are under doc/*.
  • Add twdoing when starting work on the MR.
  • Add twfinished if Technical Writing team work on the MR is complete but it remains open.

3. Maintainer

1. Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
2. Ensure a release milestone is set.
3. If there has not been a technical writer review, create an issue for one using the Doc Review template.

added 1st contribution Community contribution labels

added Technical Writing docsfix documentation labels

assigned to @rdickenson

@rdickenson can you help with the review?

@dsearles - Can you please verify this change is valid?

added twdoing label

added devopssecure groupstatic analysis labels

mentioned in issue #223826 (closed)

resolved all threads

approved this merge request

merged

mentioned in commit 26f322d1

added twfinished label and removed twdoing label

marked the checklist item Add twfinished if Technical Writing team work on the MR is complete but it remains open. as completed

marked the checklist item Add twdoing when starting work on the MR. as completed

marked the checklist item Add docs-only when the only files changed are under doc/*. as completed

marked the checklist item Ensure Technical Writing, documentation, and a docs:: scoped label are added. as completed

marked the checklist item Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage. as completed

@zzjin - Thank you for this documentation contribution. I've accepted this merge request. The change should be visible on the GitLab documentation site within 24 hours.

changed milestone to %13.4

added workflowstaging label

added workflowcanary label and removed workflowstaging label

added workflowproduction label and removed workflowcanary label

This merge request has been deployed to the pre.gitlab.com environment, and will be included in the upcoming self-managed GitLab 13.5.0 release.

---

This comment is generated automatically using the Release Tools project.

added published label

This merge request has been deployed to the release.gitlab.net environment, and will be included in the upcoming self-managed GitLab 13.5.0 release.

---

This comment is generated automatically using the Release Tools project.

added typemaintenance label