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: content/billing/how-tos/products/manage-ghas-licenses.md
-4Lines changed: 0 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,10 +40,6 @@ For information about using policies to control use of licenses in your enterpri
40
40
1. To the right of "{% data variables.product.prodname_AS %}", select {% octicon "kebab-horizontal" aria-label="Open menu" %}, then click **Cancel subscription**.
41
41
1. To confirm your cancellation, click **I understand, cancel {% data variables.product.prodname_AS %}**.
42
42
43
-
{% ifversion disable-ghas-button %}
44
-
45
43
## Disabling {% data variables.product.prodname_GHAS %} in an enterprise
46
44
47
45
Enterprise owners can disable {% data variables.product.prodname_GHAS %} completely and set a policy to prevent future re-enablement. See [AUTOTITLE](/billing/how-tos/products/disable-ghas-for-enterprise).
Copy file name to clipboardExpand all lines: content/code-security/concepts/code-scanning/about-code-scanning-alerts.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,6 +64,8 @@ If you configure {% data variables.product.prodname_code_scanning %} using {% da
64
64
65
65
When {% data variables.product.prodname_code_scanning %} reports data-flow alerts, {% data variables.product.prodname_dotcom %} shows you how data moves through the code. {% data variables.product.prodname_code_scanning_caps %} allows you to identify the areas of your code that leak sensitive information, and that could be the entry point for attacks by malicious users.
66
66
67
+
In some cases, the same vulnerability can be reached through multiple code paths, for example, when several different functions pass user input to the same unsafe operation. {% data variables.product.prodname_code_scanning_caps %} groups these related paths under a single alert rather than creating separate alerts for each path, so you can see the full scope of the vulnerability in one place.
68
+
67
69
{% data reusables.code-scanning.track-alert-in-issue %}
Copy file name to clipboardExpand all lines: content/code-security/how-tos/manage-security-alerts/manage-code-scanning-alerts/assessing-code-scanning-alerts-for-your-repository.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,10 +31,14 @@ By default, the {% data variables.product.prodname_code_scanning %} alerts page
31
31
32
32
{% data reusables.code-scanning.explore-alert %}
33
33
{% data reusables.code-scanning.alert-default-branch %}
34
-
1. Optionally, if the alert highlights a problem with data flow, click **Show paths** to display the path from the data source to the sink where it's used.
34
+
1. Optionally, if the alert highlights a problem with data flow, click **Show paths** to display the path from the data source to the sink where it's used. The path view shows each step in the data flow as a numbered list, from the point where user-provided data enters the code (the source) to the point where it's used in a potentially unsafe operation (the sink).
35
35
36
36
37
37
38
+
Some alerts identify multiple paths through the code that could trigger the same vulnerability. When an alert has multiple paths, a dropdown appears above the path view showing the number of paths available. You can select each path from the dropdown to review it individually.
39
+
40
+
41
+
38
42
1. Alerts from {% data variables.product.prodname_codeql %} analysis include a description of the problem. Click **Show more** for guidance on how to fix your code.
Copy file name to clipboardExpand all lines: content/code-security/reference/supply-chain-security/dependabot-options-reference.md
+45-29Lines changed: 45 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -218,42 +218,58 @@ You can specify the duration of the cooldown using the options below.
218
218
| `include` | List of dependencies to **apply cooldown** (up to **150 items**). Supports wildcards (`*`). |
219
219
| `exclude` | List of dependencies **excluded from cooldown** (up to **150 items**). Supports wildcards (`*`). |
220
220
221
-
The table below shows the package managers for which SemVer is supported.
221
+
The table below shows the package managers that support `cooldown`. The `default-days` option is supported for all package managers listed, while `semver-major-days`, `semver-minor-days`, and `semver-patch-days` are supported only where indicated.
222
222
223
-
| Package manager | SemVer supported |
224
-
|-----------------------|------------------|
223
+
| Package manager | Default days supported | SemVer-bump days supported |
Copy file name to clipboardExpand all lines: content/copilot/reference/copilot-usage-metrics/copilot-usage-metrics.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,6 +80,7 @@ For example schemas of the data returned by the APIs, see [AUTOTITLE](/copilot/r
80
80
|`chat_panel_ask_mode`| Captures user-initiated interactions in the chat panel with ask mode selected. |
81
81
|`chat_panel_custom_mode`| Captures user-initiated interactions in the chat panel with a custom agent selected. |
82
82
|`chat_panel_edit_mode`| Captures user-initiated interactions in the chat panel with edit mode selected. |
83
+
|`chat_panel_plan_mode`| Captures user-initiated interactions in the chat panel with plan mode selected. |
83
84
|`chat_panel_unknown_mode`| Captures user-initiated interactions in the chat panel where the mode is unknown. |
84
85
|`code_generation_activity_count`| Number of distinct {% data variables.product.prodname_copilot_short %} output events generated. <br><br> **Includes:** All generated content, including comments and docstrings. <br> **Multiple blocks:** Each distinct code block from a single user prompt counts as a separate generation. <br> **Note:** This metric is not directly comparable to `user_initiated_interaction_count`, since one prompt can produce multiple generations. |
85
86
|`code_acceptance_activity_count`| Number of suggestions or code blocks accepted by users. <br><br> **Counts:** All built-in accept actions, such as “apply to file,” “insert at cursor,” “insert into terminal,” and use of the **Copy** button. <br> **Does not count:** Manual OS clipboard actions (for example, <kbd>Ctrl</kbd>+<kbd>C</kbd>). <br> **Granularity:** Each acceptance action increments the count once, regardless of how many code blocks were generated by the initial prompt. |
Copy file name to clipboardExpand all lines: content/copilot/tutorials/use-an-ai-sme.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ When you start work on an unfamiliar codebase, or you're asked to change a part
20
20
21
21
When you need to understand an unfamiliar codebase, you usually rely on a teammate who knows the code. When that person isn't available, {% data variables.copilot.copilot_cli_short %} can fill the gap. In this tutorial, you'll ask {% data variables.copilot.copilot_cli_short %} questions about a repository's code, learn prompting techniques that produce code-grounded answers, and build the confidence to start making changes.
22
22
23
-
## When to use an AI SME (or even When do I use an AI SME?)
23
+
## When to use an AI SME
24
24
25
25
This tutorial is useful any time you need to understand a codebase faster. For example:
0 commit comments