Skip to content

Commit 9f3e101

Browse files
authoredJan 14, 2025
Hack week 2025: fix "alt text length" warnings in code-security (#53854)
1 parent e16332a commit 9f3e101

File tree

14 files changed

+21
-21
lines changed

14 files changed

+21
-21
lines changed
 

‎content/code-security/code-scanning/managing-code-scanning-alerts/about-code-scanning-alerts.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ Each alert highlights a problem with the code and the name of the tool that iden
5050

5151
{% data reusables.code-scanning.alert-default-branch %}
5252

53-
![Screenshot showing the elements of a {% data variables.product.prodname_code_scanning %} alert, including the title of the alert and relevant lines of code at left and the severity level, affected branches, and weaknesses at right. ](/assets/images/help/repository/code-scanning-alert.png)
53+
![Screenshot of a {% data variables.product.prodname_code_scanning %} alert, includes the alert title, relevant lines of code at the left, metadata at the right.](/assets/images/help/repository/code-scanning-alert.png)
5454

5555
If you configure {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, you can also find data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information.
5656

‎content/code-security/code-scanning/managing-code-scanning-alerts/tracking-code-scanning-alerts-in-issues-using-task-lists.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ You can use more than one issue to track the same {% data variables.product.prod
3232

3333
* The {% data variables.product.prodname_code_scanning %} alerts list page will show which alerts are tracked in issues so that you can view at a glance which alerts still require processing and how many issues they are tracked in.
3434

35-
![Screenshot of the {% data variables.product.prodname_code_scanning %} alerts view. The first entry includes the issue icon followed by the number 2. The third entry includes the issue icon followed by the number 1. Both are outlined in dark orange.](/assets/images/help/repository/code-scanning-alert-list-tracked-issues.png)
35+
![Screenshot of {% data variables.product.prodname_code_scanning %} alerts view. The first and third entries include the issue icon with the issue number.](/assets/images/help/repository/code-scanning-alert-list-tracked-issues.png)
3636

3737
* A "tracked in" section will also show in the corresponding alert page.
3838

@@ -45,7 +45,7 @@ You can use more than one issue to track the same {% data variables.product.prod
4545
4646
The color of the icon is grey because an alert has a status of "open" or "closed" on every branch. The issue tracks an alert, so the alert cannot have a single open/closed state in the issue. If the alert is closed on one branch, the icon color will not change.
4747

48-
![Screenshot showing an issue that tracks a {% data variables.product.prodname_code_scanning %} alert. The hovercard for the alert is displayed, with a grey security badge icon preceding the title.](/assets/images/help/repository/code-scanning-tracking-issue-hovercard.png)
48+
![Screenshot of an issue that tracks a {% data variables.product.prodname_code_scanning %} alert. The hovercard is displayed, with a grey security badge icon.](/assets/images/help/repository/code-scanning-tracking-issue-hovercard.png)
4949

5050
The status of the tracked alert won't change if you change the checkbox state of the corresponding task list item (checked/unchecked) in the issue.
5151

‎content/code-security/code-scanning/managing-code-scanning-alerts/triaging-code-scanning-alerts-in-pull-requests.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -133,7 +133,7 @@ When {% data variables.product.prodname_copilot_autofix_short %} is enabled for
133133
134134
Usually, when you suggest changes to a pull request, your comment contains changes for a single file that is changed in the pull request. The following screenshot shows an {% data variables.product.prodname_copilot_autofix_short %} comment that suggests changes to the `index.js` file where the alert is displayed. Since the potential fix requires a new dependency on `escape-html`, the comment also suggests adding this dependency to the `package.json` file, even though the original pull request makes no changes to this file.
135135

136-
![Screenshot of the {% data variables.product.prodname_copilot_autofix_short %} suggestion with explanation and change in the current file. A suggested change in "package.json" is outlined in dark orange.](/assets/images/help/code-scanning/autofix-example.png)
136+
![Screenshot of {% data variables.product.prodname_copilot_autofix_short %} suggestion to edit the current file. A suggested change in "package.json" is outlined in dark orange.](/assets/images/help/code-scanning/autofix-example.png)
137137

138138
### Assessing and committing an {% data variables.product.prodname_copilot_autofix_short %} suggestion
139139

‎content/code-security/code-scanning/troubleshooting-code-scanning/advanced-security-must-be-enabled.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ If you are on a free, pro, or team plan, you can only use {% data variables.prod
3939
1. If there is an associated and active **Enable** button, {% data variables.product.prodname_GH_advanced_security %} is available for this repository but not yet enabled.
4040
1. If use of {% data variables.product.prodname_GH_advanced_security %} is blocked by a policy, the **Enable** button is inactive and the owner of the policy is listed.
4141

42-
![Screenshot of the "{% data variables.product.prodname_GH_advanced_security %}" setting. The owner of the enterprise policy and the inactive "Enable" button are highlighted with a dark orange outline.](/assets/images/help/repository/ghas-enterprise-policy-block.png)
42+
![Screenshot of the "{% data variables.product.prodname_GH_advanced_security %}" setting. The owner of the enterprise policy and the inactive "Enable" button are outlined in orange.](/assets/images/help/repository/ghas-enterprise-policy-block.png)
4343

4444
## Fixing the problem
4545

‎content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/using-the-codeql-model-editor.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -61,11 +61,11 @@ This section uses an open source Java project called "sofa-jraft" as an example.
6161

6262
1. Display the {% data variables.product.prodname_codeql %} model editor. By default the editor runs in application mode, so the list of external APIs used by the selected codebase is shown.
6363

64-
![Screenshot of the "Application mode" view of the CodeQL model pack editor in Visual Studio Code showing two of the external Java frameworks used by the "sofa-jraft" codebase.](/assets/images/help/security/codeql-for-vs-code-model-application-mode.png)
64+
![Screenshot of the "Application mode" view showing two of the external Java frameworks used by the "sofa-jraft" codebase.](/assets/images/help/security/codeql-for-vs-code-model-application-mode.png)
6565

6666
1. Click to expand an external API and view the list of calls from the codebase to the external dependency.
6767

68-
![Screenshot of the "Application mode" view of the CodeQL model pack editor in Visual Studio Code showing the calls to the "rocksdbjni" framework ready for modeling. The "View" option for the first call is highlighted with a dark orange outline.](/assets/images/help/security/codeql-for-vs-code-model-application-mode-expanded.png)
68+
![Screenshot of "Application mode" showing the calls to the "rocksdbjni" framework. The "View" option for the first call is outlined in orange.](/assets/images/help/security/codeql-for-vs-code-model-application-mode-expanded.png)
6969

7070
1. Click **View** associated with an API call or method to show where it is used in your codebase.
7171

@@ -104,13 +104,13 @@ This section uses an open source Java project called "sofa-jraft" as an example.
104104

105105
1. Display the {% data variables.product.prodname_codeql %} model editor. By default the editor runs in application mode. Click **Model as dependency** to display dependency mode. The screen changes to show the public API of the framework or library.
106106

107-
![Screenshot of the "Dependency mode" view of the CodeQL model pack editor in Visual Studio Code showing three of the packages published by the "sofa-jraft" codebase.](/assets/images/help/security/codeql-for-vs-code-model-dependency-mode.png)
107+
![Screenshot of the "Dependency mode" view showing three of the packages published by the "sofa-jraft" codebase.](/assets/images/help/security/codeql-for-vs-code-model-dependency-mode.png)
108108

109109
1. Click to expand a package and view the list of available methods.
110110

111111
1. Click **View** associated with a method to show its definition.
112112

113-
![Screenshot of the "Dependency mode" view of the CodeQL model pack editor in Visual Studio Code showing one model for the "com.alipay.sofa.jraft.option.BallotBoxOptions.getClosureQueue()" method. The "+" button is outlined in dark orange. Click this button to create a second model for the method.](/assets/images/help/security/codeql-for-vs-code-model-dependency-mode-expanded.png)
113+
![Screenshot of "Dependency mode" with one model for "com.alipay.sofa.jraft.option.BallotBoxOptions.getClosureQueue()". The "+" button is outlined.](/assets/images/help/security/codeql-for-vs-code-model-dependency-mode-expanded.png)
114114

115115
1. When you have determined how to model the method, define the "Model type".
116116

@@ -141,7 +141,7 @@ The editor will create a separate model file for each package that you model.
141141

142142
Some methods support more than one data flow. It is important to model all the data flows for a method, otherwise you cannot detect all the potential problems associated with using the method. First you model one data flow for the method, and then use the **+** button in the method row to specify a second data flow model.
143143

144-
![Screenshot of the "Dependency mode" view of the CodeQL model pack editor in Visual Studio Code showing the public methods available in the "com.alipay.soft.jraft.option" package ready for modeling. The "View" option for the first method is highlighted with a dark orange outline.](/assets/images/help/security/codeql-for-vs-code-model-dependency-mode-plus.png)
144+
![Screenshot of the "Dependency mode" view with public methods available in "com.alipay.soft.jraft.option". A "View" option is outlined in orange.](/assets/images/help/security/codeql-for-vs-code-model-dependency-mode-plus.png)
145145

146146
## Testing {% data variables.product.prodname_codeql %} model packs in {% data variables.product.prodname_vscode_shortname %}
147147

‎content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ You can configure notification settings for yourself or your organization from t
4848
{% data reusables.notifications.vulnerable-dependency-notification-options %}
4949

5050
{% ifversion update-notification-settings-22 %}
51-
![Screenshot of the notification options for {% data variables.product.prodname_dependabot_alerts %}. A dropdown menu, showing notification frequency options, is highlighted with an orange outline.](/assets/images/help/dependabot/dependabot-notification-frequency.png){% endif %}{% ifversion ghes %}
51+
![Screenshot of the notification options for {% data variables.product.prodname_dependabot_alerts %}. A dropdown menu with frequency options is outlined in orange.](/assets/images/help/dependabot/dependabot-notification-frequency.png){% endif %}{% ifversion ghes %}
5252
![Screenshot of the notification options for {% data variables.product.prodname_dependabot_alerts %}.](/assets/images/help/enterprises/dependabot-alerts-options-no-ui.png){% endif %}
5353

5454
> [!NOTE]

‎content/code-security/getting-started/quickstart-for-securing-your-organization.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -104,7 +104,7 @@ You can choose to enable a security feature automatically in all new repositorie
104104
1. In the left sidebar, click **{% octicon "codescan" aria-hidden="true" %} Code security and analysis**.
105105
1. Below the name of the feature, select the option for automatically enabling the feature in applicable future repositories.
106106

107-
![Screenshot of "Code security and analysis" page. Below "Dependabot alerts", a checkbox to enable the feature in future repositories is highlighted in orange.](/assets/images/help/security/enable-for-new-repos.png)
107+
![Screenshot of "Code security and analysis" page. Below "Dependabot alerts", the checkbox to enable alerts in new repositories is outlined in orange.](/assets/images/help/security/enable-for-new-repos.png)
108108

109109
## Monitoring the impact of security features
110110

‎content/code-security/secret-scanning/managing-alerts-from-secret-scanning/monitoring-alerts.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ In addition to displaying an alert in the **Security** tab of the repository, {%
3434
1. On your notification settings page, under "Subscriptions", then under "Watching", select the **Notify me** dropdown.
3535
1. Select "Email" as a notification option, then click **Save**.
3636

37-
![Screenshot of the notification settings for a user account. An element header, titled "Subscriptions", and a sub-header, titled "Watching", are shown. A checkbox, titled "Email", is highlighted with an orange outline.](/assets/images/help/notifications/repository-watching-notification-options.png)
37+
![Screenshot of the notification settings for a user account. Under "Subscriptions" and "Watching" a checkbox, titled "Email", is outlined in orange.](/assets/images/help/notifications/repository-watching-notification-options.png)
3838

3939
{% data reusables.notifications.watch-settings %}
4040

‎content/code-security/secret-scanning/secret-scanning-partnership-program/secret-scanning-partner-program.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ To scan for your secrets, {% data variables.product.prodname_dotcom %} needs the
5656
* High entropy random strings
5757
* A 32-bit checksum
5858

59-
![Screenshot showing the breakdown of a secret into details to be considered when submitting to GitHub a regular expression to find high quality secrets.](/assets/images/help/security/regular-expression-guidance.png)
59+
![Screenshot showing the breakdown of a secret into a prefix and a 32-bit checksum.](/assets/images/help/security/regular-expression-guidance.png)
6060

6161
* A test account for your service. This will allow us to generate and analyze examples of the secrets, further reducing false positives.
6262
* The URL of the endpoint that receives messages from {% data variables.product.prodname_dotcom %}. The URL doesn't have to be unique for each secret type.

‎content/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/best-practices-for-writing-repository-security-advisories.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ For examples showing how affected versions are defined in some existing advisori
105105
106106
* You cannot specify multiple affected version ranges in the same field, such as `> 2.0, < 2.3, > 3.0, < 3.2`.To specify more than one range, you must create a new **Affected products** section for each range, by clicking the **+ Add another affected product** button.
107107

108-
![Screenshot of the "Affected products" area of the security advisory form. A link, labeled "Add another affected product", is highlighted with a dark orange outline.](/assets/images/help/security/security-advisory-add-another-affected-product.png)
108+
![Screenshot of the "Affected products" area of the security advisory form. The "Add another affected product" link is outlined in dark orange.](/assets/images/help/security/security-advisory-add-another-affected-product.png)
109109
* If the affected version range includes only a single upper or lower bound:
110110
* The implicit value is always `> 0` if the lower bound is not explicitly specified.
111111
* The implicit value is always infinity if the upper bound is not explicitly specified.

‎content/code-security/security-advisories/working-with-repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ To keep information about vulnerabilities secure, integrations, including CI, ca
3737
1. In the "Security Advisories" list, click the name of the security advisory you'd like to create a temporary private fork in.
3838
1. Scroll to the bottom of the advisory form and click **Start a temporary private fork**.
3939

40-
![Screenshot of the "Collaborate on a patch in private" area of the form. A button, labeled "Start a temporary private fork", is outlined in dark orange.](/assets/images/help/security/new-temporary-private-fork-button.png)
40+
![Screenshot of the "Collaborate on a patch in private" area of the form. The "Start a temporary private fork" button is outlined in dark orange.](/assets/images/help/security/new-temporary-private-fork-button.png)
4141

4242
A private fork of the repository is created and shown on the advisory page.
4343

‎content/code-security/security-advisories/working-with-repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ The instructions in this article refer to enablement at repository level. For in
3131
{% data reusables.repositories.sidebar-settings %}
3232
{% data reusables.repositories.navigate-to-code-security-and-analysis %}
3333
1. Under "Code security and analysis", to the right of "Private vulnerability reporting", click **Enable** or **Disable**, to enable or disable the feature, respectively.
34-
![Screenshot of the "Code security and analysis" page, showing the "Private vulnerability reporting" setting. The "Enable" button is outlined in dark orange.](/assets/images/help/security/private-vulnerability-reporting-enable-or-disable-repo.png)
34+
![Screenshot of the "Code security and analysis" page, showing the "Private vulnerability reporting" setting. The "Enable" button is outlined in orange.](/assets/images/help/security/private-vulnerability-reporting-enable-or-disable-repo.png)
3535

3636
{% data reusables.security-advisory.private-vulnerability-reporting-security-researcher %}
3737

@@ -56,6 +56,6 @@ Notifications depend on the user's notification preferences. You will receive an
5656
1. On your notification settings page, under "Subscriptions," then under "Watching," select the **Notify me** dropdown.
5757
1. Select "Email" as a notification option, then click **Save**.
5858

59-
![Screenshot of the notification settings for a user account. An element header, titled "Subscriptions", and a sub-header, titled "Watching", are shown. A checkbox, titled "Email", is highlighted with an orange outline.](/assets/images/help/notifications/repository-watching-notification-options.png)
59+
![Screenshot of the notification settings for a user account. Under "Subscriptions" and "Watching" a checkbox, titled "Email", is outlined in orange.](/assets/images/help/notifications/repository-watching-notification-options.png)
6060

6161
{% data reusables.notifications.watch-settings %}

‎content/code-security/security-advisories/working-with-repository-security-advisories/publishing-a-repository-security-advisory.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ Publishing a security advisory deletes the temporary private fork for the securi
7070
1. In the "Security Advisories" list, click the name of the security advisory you'd like to publish.
7171
1. Scroll to the bottom of the advisory form and click **Publish advisory**.
7272

73-
![Screenshot of the "Required advisory information has been provided" area of a draft security advisory. The "Publish advisory" button is outlined in dark orange.](/assets/images/help/security/publish-advisory-button.png)
73+
![Screenshot of the "Required advisory information has been provided" area of the page. The "Publish advisory" button is outlined in orange.](/assets/images/help/security/publish-advisory-button.png)
7474

7575
> [!NOTE]
7676
> If you selected "Request CVE ID later", you will see a **Request CVE** button in place of the **Publish advisory** button. For more information, see [Requesting a CVE identification number (Optional)](#requesting-a-cve-identification-number-optional) below.
@@ -89,7 +89,7 @@ Publishing a security advisory deletes the temporary private fork for the securi
8989
1. In the "Security Advisories" list, click the name of the security advisory you'd like to request a CVE identification number for.
9090
1. Scroll to the bottom of the advisory form and click **Request CVE**.
9191

92-
![Screenshot of the "Required advisory information has been provided" area of a draft security advisory. The "Request CVE" button is outlined in dark orange.](/assets/images/help/security/security-advisory-request-cve-button.png)
92+
![Screenshot of the "Required advisory information has been provided" area of the page. The "Request CVE" button is outlined in dark orange.](/assets/images/help/security/security-advisory-request-cve-button.png)
9393

9494
## Further reading
9595

‎content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -91,7 +91,7 @@ You may notice some repositories have a "Used by" section in the sidebar of the
9191

9292
The "Used by" section shows the number of public references to the package that were found, and displays the avatars of some of the owners of the dependent projects.
9393

94-
![Screenshot of the "Used by" section for a repository. To the right of the "Used by" header is "13.4m." Under the header are 8 avatars and "+13,435,819."](/assets/images/help/repository/used-by-section.png)
94+
![Screenshot of the "Used by" section for a repository showing the summary of "13.4m" with details of 8 avatars and "+13,435,819."](/assets/images/help/repository/used-by-section.png)
9595

9696
Clicking any item in this section takes you to the **Dependents** tab of the dependency graph.
9797

0 commit comments

Comments
 (0)
Please sign in to comment.