Skip to content

Commit 5503f05

Browse files
Update broken linking (#31982)
* update broken hyperlinking * fixing link formatting --------- Co-authored-by: Michael Cretzman <[email protected]>
1 parent 416268c commit 5503f05

File tree

3 files changed

+11
-11
lines changed

3 files changed

+11
-11
lines changed

config/_default/menus/main.en.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6828,7 +6828,7 @@ menu:
68286828
url: /security/code_security/dev_tool_int/
68296829
parent: code_security
68306830
weight: 6
6831-
- name: GitHub Pull Requests
6831+
- name: Pull Request Comments
68326832
identifier: dev_tool_int_github_pull_requests
68336833
url: /security/code_security/dev_tool_int/github_pull_requests/
68346834
parent: dev_tool_int

content/en/security/code_security/static_analysis/_index.md

Lines changed: 5 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ To get started, go to the [**Code Security** setup page][12] or see the [Setup d
3838
## Integrate into the development lifecycle
3939

4040
### Source code management
41-
{{< whatsnext desc="During code reviews, Datadog can automatically flag Static Code Analysis violations in pull requests by adding inline review comments on the relevant line(s) of code. When applicable, Datadog also provides suggested fixes that can be applied directly in the pull request. You can also open a pull request directly from Datadog to fix a vulnerability or quality issue." >}}
41+
{{< whatsnext desc="During code reviews, Datadog can automatically flag Static Code Analysis violations in pull requests by adding inline review comments on the relevant line(s) of code. When applicable, Datadog also provides suggested fixes that can be applied directly in the pull request." >}}
4242
{{< nextlink href="static_analysis/github_pull_requests" >}}Pull Requests{{< /nextlink >}}
4343
{{< /whatsnext >}}
4444

@@ -55,7 +55,7 @@ After setting up Static Code Analysis, a scan is run on each commit to a scanned
5555
* The **Code Vulnerabilities** tab contains the violations found by Datadog's rules in the [Security category][2].
5656
* The **Code Quality** tab contains the violations found by Datadog's rules in the [Best Practices, Code Style, Error Prone, or Performance categories][3].
5757

58-
To filter your results, use the facets to the left of the list, or search. Results can be filtered by service or team facets. For more information about how results are linked to Datadog services and teams, see [Getting Started with Code Security][11].
58+
To filter your results, use the facets to the left of the list, or search. Results can be [filtered by service or team facets][13].
5959

6060
Every row represents a violation. Each violation is associated with the specific commit and branch that is selected in the filters at the top of the page (by default, results are shown for the latest commit on the default branch of the repository you are viewing).
6161

@@ -122,16 +122,13 @@ paths:
122122
- path/to/service/code/**
123123
{{< /code-block >}}
124124

125-
126-
## Remediation
127-
128-
### Apply suggested fixes
125+
## Apply suggested fixes
129126
<!-- {{< img src="code_security/static_analysis/static-analysis-fixes.png" alt="Fixes tab of a static analysis violation" style="width:80%;">}} -->
130127

131128
In Datadog Static Code Analysis, there are two types of suggested fixes:
132129

133130
1. **Deterministic Suggested Fix:** For simple violations like linting issues, the rule analyzer automatically provides templated fixes.
134-
2. **AI-suggested Fix:** For complex violations, fixes are typically not available beforehand. Instead, you can use AI-suggested Fixes, which use OpenAI's GPT-4 to generate a suggested fix. You can choose between "Text" and "Unified Diff" fixes, which outputs plain text instructions or a code change for resolving the violation, respectively.
131+
2. **AI-suggested Fix:** For complex violations, fixes are typically not available beforehand. Instead, you can use AI-suggested fixes, which use OpenAI's GPT-4 to generate a suggested fix. You can choose between "Text" and "Unified Diff" fixes, which outputs plain text instructions or a code change for resolving the violation, respectively.
135132

136133
<!-- {{< img src="code_security/static_analysis/static-analysis-default-fix.png" alt="Visual indicator of a default static analysis suggested fix" style="width:60%;">}}
137134
@@ -183,3 +180,4 @@ If you believe a specific violation is a false positive, you can flag it as a fa
183180
[10]: /security/code_security/dev_tool_int/github_pull_requests/
184181
[11]: /getting_started/code_security/
185182
[12]: https://app.datadoghq.com/security/configuration/code-security/setup
183+
[13]: https://docs.datadoghq.com/security/code_security/static_analysis/#link-results-to-datadog-services-and-teams

content/en/security/code_security/static_analysis/setup/_index.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -24,9 +24,9 @@ To set up Datadog SAST in-app, navigate to [**Security** > **Code Security**][1]
2424
### Scan with Datadog-hosted scanning
2525

2626
You can run Datadog Static Code Analysis (SAST) scans directly on Datadog infrastructure. Supported repository types include:
27-
- [GitHub](/security/code_security/static_analysis/setup/?tab=github) (excluding repositories that use [Git Large File Storage][17])
28-
- [GitLab.com and GitLab Self-Managed](https://docs.datadoghq.com/security/code_security/static_analysis/setup/?tab=gitlab)
29-
- [Azure DevOps](https://docs.datadoghq.com/security/code_security/static_analysis/setup/?tab=azuredevops)
27+
- [GitHub][18] (excluding repositories that use [Git Large File Storage][17])
28+
- [GitLab.com and GitLab Self-Managed][18]
29+
- [Azure DevOps][19]
3030

3131
To get started, navigate to the [**Code Security** page][1].
3232

@@ -706,3 +706,5 @@ Datadog stores findings in accordance with our [Data Rentention Periods](https:/
706706
[15]: https://docs.oasis-open.org/sarif/sarif/v2.1.0/sarif-v2.1.0.html
707707
[16]: https://www.first.org/cvss/
708708
[17]: https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-git-large-file-storage
709+
[18]: /security/code_security/static_analysis/setup/?tab=github#select-your-source-code-management-provider
710+
[19]: /security/code_security/static_analysis/setup/?tab=azuredevops#select-your-source-code-management-provider

0 commit comments

Comments
 (0)