You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: learn-pr/github/codebase-representation-codeql/includes/5-troubleshoot-your-results.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ Here are important points to keep in mind while you're working with CodeQL and t
17
17
18
18
- CodeQL predicates and classes are evaluated to database tables. Large predicates generate large tables with many rows, so they're expensive to compute.
19
19
- The QL language is implemented through standard database operations and relational algebra, such as join, projection, and union.
20
-
- Queries are evaluated *bottom up*, which means that a predicate is not evaluated until all of the predicates that it depends on are evaluated.
20
+
- Queries are evaluated *bottom up*, which means that a predicate isn't evaluated until all of the predicates that it depends on are evaluated.
21
21
22
22
### Debug artifacts
23
23
@@ -41,7 +41,7 @@ If a workflow run for code scanning fails because of a server error, a transient
41
41
42
42
### Error: "Out of disk" or "Out of memory"
43
43
44
-
CodeQL might run out of disk or memory on the runner for very large projects. If it's a hosted GitHub Actions runner, contact GitHub support to investigate the problem. If it's a self-hosted runner, you might need to make adjustments to the server's specifications. For more information, see the [CodeQL documentation about recommended hardware for running CodeQL](https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/recommended-hardware-resources-for-running-codeql).
44
+
CodeQL might run out of disk or memory on the runner for projects that are too large. If it's a hosted GitHub Actions runner, contact GitHub support to investigate the problem. If it's a self-hosted runner, you might need to make adjustments to the server's specifications. For more information, see the [CodeQL documentation about recommended hardware for running CodeQL](https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/recommended-hardware-resources-for-running-codeql).
45
45
46
46
### Error: 403 "Resource not accessible by integration" when using Dependabot
47
47
@@ -64,7 +64,7 @@ on:
64
64
65
65
### Error: "SARIF Upload Rejected Because of Default Setup"
66
66
67
-
You get an error if a process tries to upload a SARIF file that contains results of CodeQL analysis to a repository where CodeQL default setup is enabled. This issue includes uploads through the REST API and the CodeQL CLI. SARIF uploads are blocked when CodeQL default setup is enabled, to reduce the potential for user confusion when multiple systems generate similar code-scanning alerts.
67
+
SARIF uploads are blocked when the CodeQL default setup is enabled. This error occurs when a process tries to upload a SARIF file containing CodeQL analysis results to a repository with default setup enabled. The error also occurs if the upload is done through the REST API and the CodeQL CLI. This block is in place to reduce the potential for user confusion when multiple systems generate similar code-scanning alerts.
68
68
69
69
This error occurs only for SARIF files that contain results that you create by using CodeQL. To fix this error, disable CodeQL in the repository and then retry uploading the SARIF file.
title: "Identify security vulnerabilities in your codebase by using CodeQL"
5
5
description: "Learn how to use CodeQL to analyze the code in your GitHub repository and identify security vulnerabilities."
6
-
ms.date: 05/01/2024
6
+
ms.date: 07/01/2025
7
7
author: a-a-ron
8
8
ms.author: aastewar
9
9
ms.topic: module
10
10
ms.service: github
11
11
title: Identify security vulnerabilities in your codebase by using CodeQL
12
12
summary: "In this module, you learn about CodeQL and how you can use it to analyze the code in your GitHub repository and identify security vulnerabilities."
13
13
abstract: |
14
-
By the end of this module, you'll be able to:
14
+
By the end of this module, you're able to:
15
15
- Create a database by using CodeQL to extract a single relational representation of each source file in the codebase.
16
16
- Run CodeQL in a database to find problems in your source code and find potential security vulnerabilities.
17
17
- Understand CodeQL scan results by using GitHub-created queries or your own custom queries.
0 commit comments