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-personal-account-on-github/managing-user-account-settings/managing-accessibility-settings.md
+2
Original file line number
Diff line number
Diff line change
@@ -18,6 +18,8 @@ To create an experience on {% data variables.product.github %} that fits your ne
18
18
19
19
You can decide whether you want to use some or all keyboard shortcuts, and control the display of animated images and how links are displayed.
20
20
21
+
This article will help you customize your experience on the {% data variables.product.github %} website as a whole. For information on using specific {% data variables.product.github %} products with screen readers and other assistive technologies, see the [{% data variables.product.github %} Accessibility Documentation](https://accessibility.github.com/documentation).
22
+
21
23
## Managing the appearance of links
22
24
23
25
You can control whether links in text blocks are underlined and therefore more distinguishable.
Copy file name to clipboardexpand all lines: content/billing/using-the-new-billing-platform/estimating-spending.md
+7
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,13 @@ product: '{% data reusables.billing.enhanced-billing-platform-product %}'
15
15
shortTitle: Estimate spending
16
16
---
17
17
18
+
<!-- expires 2025-04-06 -->
19
+
20
+
> [!NOTE]
21
+
> Coming April 6, 2025: Usage ingestion for {% data variables.product.github %}’s [enhanced billing platform](/billing/using-the-new-billing-platform/about-the-new-billing-platform) will change from every minute to every hour.
22
+
23
+
<!-- end expires 2025-04-06 -->
24
+
18
25
The new billing platform provides a high-level view of your spending trends based on the usage across products. You can use this information to estimate your spending and make informed decisions about your budget.
title: Enabling delegated alert dismissal for code scanning
3
+
intro: 'You can use delegated alert dismissal to control who can dismiss an alert found by {% data variables.product.prodname_code_scanning %}.'
4
+
permissions: '{% data reusables.permissions.delegated-alert-dismissal %}'
5
+
versions:
6
+
feature: security-delegated-alert-dismissal
7
+
type: how_to
8
+
topics:
9
+
- Code scanning
10
+
- Advanced Security
11
+
- Alerts
12
+
- Repositories
13
+
shortTitle: Enable delegated alert dismissal
14
+
---
15
+
16
+
## About enabling delegated alert dismissal
17
+
18
+
{% data reusables.code-scanning.delegated-alert-dismissal-beta %}
19
+
20
+
{% data reusables.security.delegated-alert-dismissal-intro %}
21
+
22
+
## Configuring delegated dismissal for a repository
23
+
24
+
>[!NOTE] If an organization owner configures delegated alert dismissal via an enforced security configuration, the settings can't be changed at the repository level.
25
+
{% data reusables.repositories.navigate-to-repo %}
26
+
{% data reusables.repositories.sidebar-settings %}
27
+
{% data reusables.repositories.navigate-to-code-security-and-analysis %}
28
+
{% data reusables.repositories.navigate-to-ghas-settings %}
29
+
30
+
1. Under "{% data variables.product.prodname_code_scanning_caps %}", toggle the option "Prevent direct alert dismissals".
31
+
32
+
## Configuring delegated dismissal for an organization
33
+
34
+
You must configure delegated dismissal for your organization using a custom security configuration. You can then apply the security configuration to all (or selected) repositories in your organization.
35
+
36
+
1. Create a new custom security configuration, or edit an existing one. See [AUTOTITLE](/code-security/securing-your-organization/enabling-security-features-in-your-organization/creating-a-custom-security-configuration#creating-a-custom-security-configuration).
37
+
1. When creating the custom security configuration, under "{% data variables.product.prodname_code_scanning_caps %}", set "Prevent direct alert dismissals" to **Enabled**.
38
+
1. Click **Save configuration**.
39
+
1. Apply the security configuration to all (or selected) repositories in your organization. See [AUTOTITLE](/code-security/securing-your-organization/enabling-security-features-in-your-organization/applying-a-custom-security-configuration).
40
+
41
+
To learn more about security configurations, see [AUTOTITLE](/code-security/securing-your-organization/introduction-to-securing-your-organization-at-scale/about-enabling-security-features-at-scale).
title: Enabling delegated alert dismissal for secret scanning
3
+
intro: 'You can use delegated alert dismissal to control who can dismiss an alert found by {% data variables.product.prodname_secret_scanning %}.'
4
+
permissions: '{% data reusables.permissions.delegated-alert-dismissal %}'
5
+
versions:
6
+
feature: security-delegated-alert-dismissal
7
+
type: how_to
8
+
topics:
9
+
- Secret scanning
10
+
- Advanced Security
11
+
- Alerts
12
+
- Repositories
13
+
shortTitle: Enable delegated alert dismissal
14
+
---
15
+
16
+
## About enabling delegated alert dismissal
17
+
18
+
{% data reusables.secret-scanning.delegated-alert-dismissal-beta %}
19
+
20
+
{% data reusables.security.delegated-alert-dismissal-intro %}
21
+
22
+
## Configuring delegated dismissal for a repository
23
+
24
+
>[!NOTE] If an organization owner configures delegated alert dismissal via an enforced security configuration, the settings can't be changed at the repository level.
25
+
{% data reusables.repositories.navigate-to-repo %}
26
+
{% data reusables.repositories.sidebar-settings %}
27
+
{% data reusables.repositories.navigate-to-code-security-and-analysis %}
28
+
{% data reusables.repositories.navigate-to-ghas-settings %}
29
+
30
+
1. Under "{% data variables.product.prodname_secret_scanning_caps %}", toggle the option "Prevent direct alert dismissals".
31
+
32
+
## Configuring delegated dismissal for an organization
33
+
34
+
You must configure delegated dismissal for your organization using a custom security configuration. You can then apply the security configuration to all (or selected) repositories in your organization.
35
+
36
+
1. Create a new custom security configuration, or edit an existing one. See [AUTOTITLE](/code-security/securing-your-organization/enabling-security-features-in-your-organization/creating-a-custom-security-configuration#creating-a-custom-security-configuration).
37
+
1. When creating the custom security configuration, under "{% data variables.product.prodname_secret_scanning_caps %}", ensure that the dropdown menus for "Alerts" and "Prevent direct alert dismissals" are set to **Enabled**.
38
+
1. Click **Save configuration**.
39
+
1. Apply the security configuration to all (or selected) repositories in your organization. See [AUTOTITLE](/code-security/securing-your-organization/enabling-security-features-in-your-organization/applying-a-custom-security-configuration).
40
+
41
+
To learn more about security configurations, see [AUTOTITLE](/code-security/securing-your-organization/introduction-to-securing-your-organization-at-scale/about-enabling-security-features-at-scale).
Copy file name to clipboardexpand all lines: content/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/index.md
Copy file name to clipboardexpand all lines: content/enterprise-onboarding/github-actions-for-your-enterprise/about-billing-for-github-actions.md
+6
Original file line number
Diff line number
Diff line change
@@ -146,6 +146,12 @@ For example, if you use 3 GB of storage for 10 days of March and 12 GB for 21 da
146
146
At the end of the month, {% data variables.product.prodname_dotcom %} rounds your storage to the nearest MB. Therefore, your storage usage for March would be 9.097 GB.
147
147
148
148
Your {% data variables.product.prodname_actions %} usage shares your account's existing billing date, payment method, and receipt. {% data reusables.dotcom_billing.view-all-subscriptions %}
149
+
<!-- expires 2025-04-06 -->
150
+
151
+
> [!NOTE]
152
+
> Coming April 6, 2025: Usage ingestion for {% data variables.product.github %}’s [enhanced billing platform](/billing/using-the-new-billing-platform/about-the-new-billing-platform) will change from every minute to every hour.
Copy file name to clipboardexpand all lines: content/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -113,7 +113,7 @@ For repository migrations, we recommend creating a test organization to use as a
113
113
1. If your source organization uses IP allow lists, configure the list to allow access by {% data variables.product.prodname_importer_proper_name %}. For more information, see [AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/managing-access-for-a-migration-between-github-products#configuring-ip-allow-lists-for-migrations).
114
114
{% data reusables.enterprise-migration-tool.trial-migrations-tasks %}
115
115
{% data reusables.enterprise-migration-tool.configure-destination-ip-allow-list %} For more information, see [AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/managing-access-for-a-migration-between-github-products#configuring-ip-allow-lists-for-migrations).
116
-
1. If you're running a repository migration and you want to migrate {% data variables.product.prodname_GH_advanced_security %} settings, enable {% data variables.product.prodname_GH_advanced_security %} for the destination organization. For more information, see [AUTOTITLE](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization).
116
+
1. If you're running a repository migration and you want to migrate settings for {% data variables.product.prodname_GHAS %}{% ifversion ghas-products %} products{% endif %}, enable {% data variables.product.prodname_GHAS %}{% ifversion ghas-products %} products{% endif %} for the destination organization. For more information, see [AUTOTITLE](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization).
117
117
1. Run your production migrations. For more information, see [AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-repositories-with-github-enterprise-importer) or [AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-organizations-with-github-enterprise-importer).
118
118
{% data reusables.enterprise-migration-tool.delete-test-organization %}
119
119
@@ -127,7 +127,7 @@ For repository migrations, we recommend creating a test organization to use as a
*[Configuring {% data variables.product.prodname_actions %}](#configuring-github-actions)
129
129
*[Configuring IP allow lists](#configuring-ip-allow-lists)
130
-
*[Managing {% data variables.product.prodname_GH_advanced_security %}](#managing-github-advanced-security)
130
+
*[Managing {% data variables.product.prodname_GHAS %} features](#managing-github-advanced-security-features)
131
131
*[Enabling webhooks](#enabling-webhooks)
132
132
*[Reinstalling {% data variables.product.prodname_github_apps %}](#reinstalling-github-apps)
133
133
*[Recreating teams](#recreating-teams)
@@ -181,9 +181,9 @@ If you added the IP ranges for {% data variables.product.prodname_importer_prope
181
181
182
182
For more information, see [AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/managing-access-for-a-migration-between-github-products#configuring-ip-allow-lists-for-migrations).
183
183
184
-
### Managing {% data variables.product.prodname_GH_advanced_security %}
184
+
### Managing {% data variables.product.prodname_GHAS %} features
185
185
186
-
If you enabled {% data variables.product.prodname_GH_advanced_security %} for the destination organization before migrating repositories, the settings for individual features were migrated. If not, you'll need to re-enable individual features after the migration. For more information, see [AUTOTITLE](/enterprise-cloud@latest/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository).
186
+
If you enabled {% data variables.product.prodname_GHAS %}{% ifversion ghas-products %} products{% endif %} for the destination organization before migrating repositories, the settings for individual features were migrated. If not, you'll need to re-enable individual features after the migration. For more information, see [AUTOTITLE](/enterprise-cloud@latest/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository).
187
187
188
188
There are additional post-migration steps for each feature.
Azure private networking supports GPU runners in the following regions.
28
30
29
31
*`EastUs`
30
-
*`WestUs`
31
32
*`NorthCentralUs`
33
+
*`WestUs`
32
34
33
35
Azure private networking supports arm64 runners in the following regions.
34
36
35
37
*`EastUs`
36
38
*`EastUs2`
39
+
*`NorthCentralUs`
37
40
*`WestUs2`
38
41
*`WestUs3`
39
-
*`NorthCentralUs`
40
42
41
43
If your desired region is not supported, please submit a request for new region availability in [this GitHub form](https://resources.github.com/private-networking-for-github-hosted-runners-with-azure-virtual-networks/). You may also use global virtual network peering to connect virtual networks across Azure regions. For more information, see [Virtual network peering](https://learn.microsoft.com/en-us/azure/virtual-network/virtual-network-peering-overview) in the Azure documentation.
> The ability to use delegated alert dismissal for {% data variables.product.prodname_code_scanning %} is currently in {% data variables.release-phases.public_preview %} and subject to change.
Organization owners, security managers, and repository administrators can enable delegated alert dismissals. Once enabled, organization owners and security managers can dismiss alerts.
> The ability to use delegated alert dismissal for {% data variables.product.prodname_secret_scanning %} is currently in {% data variables.release-phases.public_preview %} and subject to change.
Delegated alert dismissal lets you restrict which users can directly dismiss an alert. When enabled, users attempting to dismiss an alert will instead create a request for dismissal.
2
+
When this happens, security managers and organization owners will be notified via email so they can review the request and approve it or deny it. The alert will only be dismissed if the dismissal request is approved; otherwise, the alert will remain open.
3
+
4
+
When you enable this feature, only security managers and organization owners will be able to approve or deny dismissal requests for alerts.
5
+
This might create friction and you should ensure to have sufficient coverage in your security managers team before you start.
6
+
7
+
In addition, dismissal request emails are sent to all organization owners and security managers. Be sure to review these lists periodically to ensure that these are the correct people to take action on these requests.
8
+
9
+
To learn more about the security manager role, see [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization).
0 commit comments