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/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ You can add personal information about yourself in your bio, like previous place
21
21
22
22
{% data reusables.profile.profile-readme %}
23
23
24
-

24
+

Copy file name to clipboardexpand all lines: content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -45,7 +45,7 @@ Before you can connect your {% ifversion fpt or ghec %}{% data variables.product
45
45
46
46
1. Sign in to {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_dotcom_the_website %}.
47
47
1. On {% data variables.product.prodname_ghe_server %}, in the upper-right corner of any page, click your profile photo, then click **Settings**.
48
-

48
+

49
49
{% data reusables.github-connect.github-connect-tab-user-settings %}
50
50
{% data reusables.github-connect.connect-dotcom-and-enterprise %}
51
51
1. Review the resources that {% data variables.product.prodname_ghe_server %} will access from your {% data variables.product.prodname_dotcom_the_website %} account, then click **Authorize**.
@@ -55,7 +55,7 @@ Before you can connect your {% ifversion fpt or ghec %}{% data variables.product
55
55
56
56
1. Sign in to {% data variables.product.prodname_ghe_managed %} and {% data variables.product.prodname_dotcom_the_website %}.
57
57
1. On {% data variables.product.prodname_ghe_managed %}, in the upper-right corner of any page, click your profile photo, then click **Settings**.
58
-

58
+

59
59
{% data reusables.github-connect.github-connect-tab-user-settings %}
60
60
{% data reusables.github-connect.connect-dotcom-and-enterprise %}
61
61
{% data reusables.github-connect.authorize-connection %}
Copy file name to clipboardexpand all lines: content/actions/managing-workflow-runs/reviewing-deployments.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,7 @@ If you have configured environment protection rules that control whether softwar
42
42
43
43
1. Navigate to the workflow run. For more information about navigating to a workflow run, see "[AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)."
44
44
1. To the right of **Deployment protection rules**, click **Start all waiting jobs**.
45
-

45
+

46
46
1. In the pop-up window, select the environments for which you want to bypass environment protection rules.
47
47
1. Under **Leave a comment**, enter a description for bypassing the environment protection rules.
48
48
1. Click **I understand the consequences, start deploying**.
Copy file name to clipboardexpand all lines: content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -50,7 +50,7 @@ To configure provisioning for your {% data variables.enterprise.prodname_emu_ent
50
50
1. Under **Note**, give your token a descriptive name.
51
51
2. Select the **Expiration** dropdown menu, then click **No expiration**.
52
52
3. Select the **admin:enterprise** scope.
53
-

53
+

54
54
4. Click **Generate token**.
55
55
5. To copy the token to your clipboard, click {% octicon "copy" aria-label="Copy token" %}.
Copy file name to clipboardexpand all lines: content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -75,9 +75,9 @@ Organization owners and team maintainers can manage the existing connection betw
75
75
{% data reusables.organizations.specific_team %}
76
76
{% data reusables.organizations.team_settings %}
77
77
1. Optionally, under "Identity Provider Group", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}.
78
-

78
+

79
79
1. To connect an IdP group, under "Identity Provider Group", select the drop-down menu, and click an identity provider group from the list.
80
-

80
+

81
81
1. Click **Save changes**.
82
82
83
83
## Viewing IdP groups, group membership, and connected teams
Copy file name to clipboardexpand all lines: content/admin/identity-and-access-management/using-saml-for-enterprise-iam/mapping-okta-groups-to-teams.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,7 @@ You can map a team in your enterprise to an Okta group you previously pushed to
58
58
{% data reusables.organizations.specific_team %}
59
59
{% data reusables.organizations.team_settings %}
60
60
6. Under "Identity Provider Group", select the drop-down menu and click an identity provider group.
61
-

61
+

Copy file name to clipboardexpand all lines: content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -160,7 +160,7 @@ You can view a list of all dormant users {% ifversion ghes or ghae %} who have n
160
160
161
161

162
162
4. Above the list of members, click **Type**, then select the type of members you want to view.
163
-

163
+

Copy file name to clipboardexpand all lines: content/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ You can add multiple public keys to your account on {% data variables.product.pr
30
30
{% ifversion upload-expired-or-revoked-gpg-key %}
31
31
To verify as many of your commits as possible, you can add expired and revoked keys. If the key meets all other verification requirements, commits that were previously signed by any of the corresponding private keys will show as verified and indicate that their signing key is expired or revoked.
Copy file name to clipboardexpand all lines: content/billing/managing-billing-for-github-copilot/viewing-your-github-copilot-usage.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -36,4 +36,4 @@ The spending information will display the total spending for each organization f
36
36
1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**.
37
37
1. Under "{% data variables.product.prodname_copilot_short %}", view the breakdown of your {% data variables.product.prodname_copilot %} usage and upcoming changes in your organization.
38
38
39
-

39
+

Copy file name to clipboardexpand all lines: content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning-for-a-repository.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -117,7 +117,7 @@ The advanced setup for {% data variables.product.prodname_code_scanning %} is he
117
117
{% data reusables.repositories.navigate-to-repo %}
118
118
{% data reusables.repositories.actions-tab %}
119
119
1. If the repository has already at least one workflow configured and running, click **New workflow** to display starter workflows. If there are currently no workflows configured for the repository, go to the next step.
120
-

120
+

121
121
2. In the "Choose a workflow" or "Get started with {% data variables.product.prodname_actions %}" view, scroll down to the "Security" category and click **Configure** under the workflow you want to configure. You may need to click **View all** to find the security workflow you want to configure.
122
122

123
123
3. Follow any instructions in the workflow to customize it to your needs. For more general assistance about workflows, click **Documentation** on the right pane of the workflow page.
@@ -261,7 +261,7 @@ There are other situations where there may be no analysis for the latest commit
261
261
262
262
To check whether a branch has been scanned, go to the {% data variables.product.prodname_code_scanning_caps %} page, click the **Branch** drop-down and select the relevant branch.
263
263
264
-

264
+

265
265
266
266
The solution in this situation is to add the name of the base branch to the `on:push` and `on:pull_request` specification in the {% data variables.product.prodname_code_scanning %} workflow on that branch and then make a change that updates the open pull request that you want to scan.
Copy file name to clipboardexpand all lines: content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md

195
195
{%- else %}
196
196
1. Review the alert, then click **Dismiss** and choose a reason for closing the alert.
197
-

197
+

198
198
{%- endif %}
199
199
{% data reusables.code-scanning.choose-alert-dismissal-reason %}
Copy file name to clipboardexpand all lines: content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -102,7 +102,7 @@ In the detailed view for an alert, some {% data variables.product.prodname_code_
102
102
{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
103
103

104
104
{% else %}
105
-

105
+


124
124
{% else %}
125
-

125
+

126
126
{% endif %}
127
127
{% data reusables.code-scanning.choose-alert-dismissal-reason %}
Copy file name to clipboardexpand all lines: content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md
+5-5
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ The search bar also allows for full text searching of alerts and related securit
61
61
{% endif %}
62
62
63
63
{% ifversion dependabot-bulk-alerts %}
64
-
{% elsif ghes = 3.5 %}
64
+
{% elsif ghes = 3.5 %}
65
65
You can select a filter in a dropdown menu at the top of the list, then click the filter that you would like to apply.{% endif %}
@@ -94,7 +94,7 @@ For supported languages, {% data variables.product.prodname_dependabot %} automa
94
94
95
95
{% endnote %}
96
96
97
-

97
+

98
98
99
99
You can filter the view to show only alerts where {% data variables.product.prodname_dependabot %} detected at least one call to a vulnerable function using the `has:vulnerable-calls` filter in the search field.
100
100
@@ -118,7 +118,7 @@ For more information, see "[Reviewing and fixing alerts](#reviewing-and-fixing-a
118
118
1. Optionally, to filter alerts, select a filter in a dropdown menu then click the filter that you would like to apply. You can also type filters into the search bar. {% ifversion dependabot-filter-label-security-advisory %}Alternatively, to filter by label, click a label assigned to an alert to automatically apply that filter to the alert list.{% endif %} For more information about filtering and sorting alerts, see "[Prioritizing {% data variables.product.prodname_dependabot_alerts %}](#prioritizing-dependabot-alerts)."
119
119
{%- ifversion dependabot-bulk-alerts %}
120
120
121
-
{% endif %}
121
+
{% endif %}
122
122
1. Click the alert that you would like to view.
123
123
{% else %}
124
124
{% data reusables.repositories.navigate-to-repo %}
@@ -196,7 +196,7 @@ If you schedule extensive work to upgrade a dependency, or decide that an alert
196
196
4. Optionally, at the top of the list of alerts, select all alerts on the page.
197
197

198
198
5. Select the "Dismiss alerts" dropdown, and click a reason for dismissing the alerts.
199
-

199
+

200
200
201
201
{% endif %}
202
202
@@ -241,6 +241,6 @@ You can view all open alerts, and you can reopen alerts that have been previousl
241
241
When a member of your organization {% ifversion not fpt %}or enterprise {% endif %}performs an action related to {% data variables.product.prodname_dependabot_alerts %}, you can review the actions in the audit log. For more information about accessing the log, see "[AUTOTITLE](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log){% ifversion not fpt %}" and "[AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)."{% else %}."{% endif %}
242
242
{% ifversion dependabot-alerts-audit-log %}
243
243
244
-
{% endif %}
244
+
{% endif %}
245
245
246
246
Events in your audit log for {% data variables.product.prodname_dependabot_alerts %} include details such as who performed the action, what the action was, and when the action was performed. {% ifversion dependabot-alerts-audit-log %}The event also includes a link to the alert itself. When a member of your organization dismisses an alert, the event displays the dismissal reason and comment.{% endif %} For information on the {% data variables.product.prodname_dependabot_alerts %} actions, see the `repository_vulnerability_alert` category in "[AUTOTITLE](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/audit-log-events-for-your-organization#repository_vulnerability_alert-category-actions){% ifversion not fpt %}" and "[AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#repository_vulnerability_alert-category-actions)."{% else %}."{% endif %}
0 commit comments