Merge branch 'main' into copilot-enterprise-megabranch
This commit is contained in:
hubwriter
@@ -2,4 +2,3 @@ versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>3.10'
|
||||
ghae: '>3.10'
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# Reference: #7757
|
||||
# Setting to disable personal namespace repo creation for EMUs, GHES 3.7+ and GHAE 3.7+ users
|
||||
# Setting to disable personal namespace repo creation for EMUs, GHES 3.7+
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '>=3.7'
|
||||
|
||||
@@ -350,6 +350,30 @@ upcoming_changes:
|
||||
date: '2024-07-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: jdennes
|
||||
- location: PullRequest.databaseId
|
||||
description: '`databaseId` will be removed. Use `fullDatabaseId` instead.'
|
||||
reason:
|
||||
'`databaseId` will be removed because it does not support 64-bit signed
|
||||
integer identifiers.'
|
||||
date: '2024-07-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: JanKoszewski
|
||||
- location: PullRequestReview.databaseId
|
||||
description: '`databaseId` will be removed. Use `fullDatabaseId` instead.'
|
||||
reason:
|
||||
'`databaseId` will be removed because it does not support 64-bit signed
|
||||
integer identifiers.'
|
||||
date: '2024-07-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: JanKoszewski
|
||||
- location: PullRequestReviewComment.databaseId
|
||||
description: '`databaseId` will be removed. Use `fullDatabaseId` instead.'
|
||||
reason:
|
||||
'`databaseId` will be removed because it does not support 64-bit signed
|
||||
integer identifiers.'
|
||||
date: '2024-07-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: JanKoszewski
|
||||
- location: TeamDiscussion.authorAssociation
|
||||
description:
|
||||
'`authorAssociation` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
|
||||
|
||||
@@ -6219,17 +6219,20 @@ input CreateAttributionInvitationInput {
|
||||
"""
|
||||
The Node ID of the owner scoping the reattributable data.
|
||||
"""
|
||||
ownerId: ID! @possibleTypes(concreteTypes: ["Bot", "Enterprise", "Mannequin", "Organization", "User"])
|
||||
ownerId: ID!
|
||||
@possibleTypes(concreteTypes: ["Bot", "Enterprise", "Mannequin", "Organization", "User"], abstractType: "Account")
|
||||
|
||||
"""
|
||||
The Node ID of the account owning the data to reattribute.
|
||||
"""
|
||||
sourceId: ID! @possibleTypes(concreteTypes: ["Bot", "Enterprise", "Mannequin", "Organization", "User"])
|
||||
sourceId: ID!
|
||||
@possibleTypes(concreteTypes: ["Bot", "Enterprise", "Mannequin", "Organization", "User"], abstractType: "Account")
|
||||
|
||||
"""
|
||||
The Node ID of the account which may claim the data.
|
||||
"""
|
||||
targetId: ID! @possibleTypes(concreteTypes: ["Bot", "Enterprise", "Mannequin", "Organization", "User"])
|
||||
targetId: ID!
|
||||
@possibleTypes(concreteTypes: ["Bot", "Enterprise", "Mannequin", "Organization", "User"], abstractType: "Account")
|
||||
}
|
||||
|
||||
"""
|
||||
@@ -28582,6 +28585,9 @@ type PullRequest implements Assignable & Closable & Comment & Labelable & Lockab
|
||||
Identifies the primary key from the database.
|
||||
"""
|
||||
databaseId: Int
|
||||
@deprecated(
|
||||
reason: "`databaseId` will be removed because it does not support 64-bit signed integer identifiers. Use `fullDatabaseId` instead. Removal on 2024-07-01 UTC."
|
||||
)
|
||||
|
||||
"""
|
||||
The number of deletions in this pull request.
|
||||
@@ -28618,6 +28624,11 @@ type PullRequest implements Assignable & Closable & Comment & Labelable & Lockab
|
||||
last: Int
|
||||
): PullRequestChangedFileConnection
|
||||
|
||||
"""
|
||||
Identifies the primary key from the database as a BigInt.
|
||||
"""
|
||||
fullDatabaseId: BigInt
|
||||
|
||||
"""
|
||||
Identifies the head Ref associated with the pull request.
|
||||
"""
|
||||
@@ -29782,12 +29793,20 @@ type PullRequestReview implements Comment & Deletable & Minimizable & Node & Rea
|
||||
Identifies the primary key from the database.
|
||||
"""
|
||||
databaseId: Int
|
||||
@deprecated(
|
||||
reason: "`databaseId` will be removed because it does not support 64-bit signed integer identifiers. Use `fullDatabaseId` instead. Removal on 2024-07-01 UTC."
|
||||
)
|
||||
|
||||
"""
|
||||
The actor who edited the comment.
|
||||
"""
|
||||
editor: Actor
|
||||
|
||||
"""
|
||||
Identifies the primary key from the database as a BigInt.
|
||||
"""
|
||||
fullDatabaseId: BigInt
|
||||
|
||||
"""
|
||||
The Node ID of the PullRequestReview object
|
||||
"""
|
||||
@@ -30024,6 +30043,9 @@ type PullRequestReviewComment implements Comment & Deletable & Minimizable & Nod
|
||||
Identifies the primary key from the database.
|
||||
"""
|
||||
databaseId: Int
|
||||
@deprecated(
|
||||
reason: "`databaseId` will be removed because it does not support 64-bit signed integer identifiers. Use `fullDatabaseId` instead. Removal on 2024-07-01 UTC."
|
||||
)
|
||||
|
||||
"""
|
||||
The diff hunk to which the comment applies.
|
||||
@@ -30040,6 +30062,11 @@ type PullRequestReviewComment implements Comment & Deletable & Minimizable & Nod
|
||||
"""
|
||||
editor: Actor
|
||||
|
||||
"""
|
||||
Identifies the primary key from the database as a BigInt.
|
||||
"""
|
||||
fullDatabaseId: BigInt
|
||||
|
||||
"""
|
||||
The Node ID of the PullRequestReviewComment object
|
||||
"""
|
||||
|
||||
@@ -472,6 +472,30 @@ upcoming_changes:
|
||||
date: '2024-07-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: jdennes
|
||||
- location: PullRequest.databaseId
|
||||
description: '`databaseId` will be removed. Use `fullDatabaseId` instead.'
|
||||
reason:
|
||||
'`databaseId` will be removed because it does not support 64-bit signed
|
||||
integer identifiers.'
|
||||
date: '2024-07-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: JanKoszewski
|
||||
- location: PullRequestReview.databaseId
|
||||
description: '`databaseId` will be removed. Use `fullDatabaseId` instead.'
|
||||
reason:
|
||||
'`databaseId` will be removed because it does not support 64-bit signed
|
||||
integer identifiers.'
|
||||
date: '2024-07-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: JanKoszewski
|
||||
- location: PullRequestReviewComment.databaseId
|
||||
description: '`databaseId` will be removed. Use `fullDatabaseId` instead.'
|
||||
reason:
|
||||
'`databaseId` will be removed because it does not support 64-bit signed
|
||||
integer identifiers.'
|
||||
date: '2024-07-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: JanKoszewski
|
||||
- location: TeamDiscussion.authorAssociation
|
||||
description:
|
||||
'`authorAssociation` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
|
||||
|
||||
@@ -6686,17 +6686,20 @@ input CreateAttributionInvitationInput {
|
||||
"""
|
||||
The Node ID of the owner scoping the reattributable data.
|
||||
"""
|
||||
ownerId: ID! @possibleTypes(concreteTypes: ["Bot", "Enterprise", "Mannequin", "Organization", "User"])
|
||||
ownerId: ID!
|
||||
@possibleTypes(concreteTypes: ["Bot", "Enterprise", "Mannequin", "Organization", "User"], abstractType: "Account")
|
||||
|
||||
"""
|
||||
The Node ID of the account owning the data to reattribute.
|
||||
"""
|
||||
sourceId: ID! @possibleTypes(concreteTypes: ["Bot", "Enterprise", "Mannequin", "Organization", "User"])
|
||||
sourceId: ID!
|
||||
@possibleTypes(concreteTypes: ["Bot", "Enterprise", "Mannequin", "Organization", "User"], abstractType: "Account")
|
||||
|
||||
"""
|
||||
The Node ID of the account which may claim the data.
|
||||
"""
|
||||
targetId: ID! @possibleTypes(concreteTypes: ["Bot", "Enterprise", "Mannequin", "Organization", "User"])
|
||||
targetId: ID!
|
||||
@possibleTypes(concreteTypes: ["Bot", "Enterprise", "Mannequin", "Organization", "User"], abstractType: "Account")
|
||||
}
|
||||
|
||||
"""
|
||||
@@ -35282,6 +35285,9 @@ type PullRequest implements Assignable & Closable & Comment & Labelable & Lockab
|
||||
Identifies the primary key from the database.
|
||||
"""
|
||||
databaseId: Int
|
||||
@deprecated(
|
||||
reason: "`databaseId` will be removed because it does not support 64-bit signed integer identifiers. Use `fullDatabaseId` instead. Removal on 2024-07-01 UTC."
|
||||
)
|
||||
|
||||
"""
|
||||
The number of deletions in this pull request.
|
||||
@@ -35318,6 +35324,11 @@ type PullRequest implements Assignable & Closable & Comment & Labelable & Lockab
|
||||
last: Int
|
||||
): PullRequestChangedFileConnection
|
||||
|
||||
"""
|
||||
Identifies the primary key from the database as a BigInt.
|
||||
"""
|
||||
fullDatabaseId: BigInt
|
||||
|
||||
"""
|
||||
Identifies the head Ref associated with the pull request.
|
||||
"""
|
||||
@@ -36557,12 +36568,20 @@ type PullRequestReview implements Comment & Deletable & Minimizable & Node & Rea
|
||||
Identifies the primary key from the database.
|
||||
"""
|
||||
databaseId: Int
|
||||
@deprecated(
|
||||
reason: "`databaseId` will be removed because it does not support 64-bit signed integer identifiers. Use `fullDatabaseId` instead. Removal on 2024-07-01 UTC."
|
||||
)
|
||||
|
||||
"""
|
||||
The actor who edited the comment.
|
||||
"""
|
||||
editor: Actor
|
||||
|
||||
"""
|
||||
Identifies the primary key from the database as a BigInt.
|
||||
"""
|
||||
fullDatabaseId: BigInt
|
||||
|
||||
"""
|
||||
The Node ID of the PullRequestReview object
|
||||
"""
|
||||
@@ -36799,6 +36818,9 @@ type PullRequestReviewComment implements Comment & Deletable & Minimizable & Nod
|
||||
Identifies the primary key from the database.
|
||||
"""
|
||||
databaseId: Int
|
||||
@deprecated(
|
||||
reason: "`databaseId` will be removed because it does not support 64-bit signed integer identifiers. Use `fullDatabaseId` instead. Removal on 2024-07-01 UTC."
|
||||
)
|
||||
|
||||
"""
|
||||
The diff hunk to which the comment applies.
|
||||
@@ -36815,6 +36837,11 @@ type PullRequestReviewComment implements Comment & Deletable & Minimizable & Nod
|
||||
"""
|
||||
editor: Actor
|
||||
|
||||
"""
|
||||
Identifies the primary key from the database as a BigInt.
|
||||
"""
|
||||
fullDatabaseId: BigInt
|
||||
|
||||
"""
|
||||
The Node ID of the PullRequestReviewComment object
|
||||
"""
|
||||
|
||||
@@ -472,6 +472,30 @@ upcoming_changes:
|
||||
date: '2024-07-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: jdennes
|
||||
- location: PullRequest.databaseId
|
||||
description: '`databaseId` will be removed. Use `fullDatabaseId` instead.'
|
||||
reason:
|
||||
'`databaseId` will be removed because it does not support 64-bit signed
|
||||
integer identifiers.'
|
||||
date: '2024-07-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: JanKoszewski
|
||||
- location: PullRequestReview.databaseId
|
||||
description: '`databaseId` will be removed. Use `fullDatabaseId` instead.'
|
||||
reason:
|
||||
'`databaseId` will be removed because it does not support 64-bit signed
|
||||
integer identifiers.'
|
||||
date: '2024-07-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: JanKoszewski
|
||||
- location: PullRequestReviewComment.databaseId
|
||||
description: '`databaseId` will be removed. Use `fullDatabaseId` instead.'
|
||||
reason:
|
||||
'`databaseId` will be removed because it does not support 64-bit signed
|
||||
integer identifiers.'
|
||||
date: '2024-07-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: JanKoszewski
|
||||
- location: TeamDiscussion.authorAssociation
|
||||
description:
|
||||
'`authorAssociation` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
|
||||
|
||||
@@ -6686,17 +6686,20 @@ input CreateAttributionInvitationInput {
|
||||
"""
|
||||
The Node ID of the owner scoping the reattributable data.
|
||||
"""
|
||||
ownerId: ID! @possibleTypes(concreteTypes: ["Bot", "Enterprise", "Mannequin", "Organization", "User"])
|
||||
ownerId: ID!
|
||||
@possibleTypes(concreteTypes: ["Bot", "Enterprise", "Mannequin", "Organization", "User"], abstractType: "Account")
|
||||
|
||||
"""
|
||||
The Node ID of the account owning the data to reattribute.
|
||||
"""
|
||||
sourceId: ID! @possibleTypes(concreteTypes: ["Bot", "Enterprise", "Mannequin", "Organization", "User"])
|
||||
sourceId: ID!
|
||||
@possibleTypes(concreteTypes: ["Bot", "Enterprise", "Mannequin", "Organization", "User"], abstractType: "Account")
|
||||
|
||||
"""
|
||||
The Node ID of the account which may claim the data.
|
||||
"""
|
||||
targetId: ID! @possibleTypes(concreteTypes: ["Bot", "Enterprise", "Mannequin", "Organization", "User"])
|
||||
targetId: ID!
|
||||
@possibleTypes(concreteTypes: ["Bot", "Enterprise", "Mannequin", "Organization", "User"], abstractType: "Account")
|
||||
}
|
||||
|
||||
"""
|
||||
@@ -35282,6 +35285,9 @@ type PullRequest implements Assignable & Closable & Comment & Labelable & Lockab
|
||||
Identifies the primary key from the database.
|
||||
"""
|
||||
databaseId: Int
|
||||
@deprecated(
|
||||
reason: "`databaseId` will be removed because it does not support 64-bit signed integer identifiers. Use `fullDatabaseId` instead. Removal on 2024-07-01 UTC."
|
||||
)
|
||||
|
||||
"""
|
||||
The number of deletions in this pull request.
|
||||
@@ -35318,6 +35324,11 @@ type PullRequest implements Assignable & Closable & Comment & Labelable & Lockab
|
||||
last: Int
|
||||
): PullRequestChangedFileConnection
|
||||
|
||||
"""
|
||||
Identifies the primary key from the database as a BigInt.
|
||||
"""
|
||||
fullDatabaseId: BigInt
|
||||
|
||||
"""
|
||||
Identifies the head Ref associated with the pull request.
|
||||
"""
|
||||
@@ -36557,12 +36568,20 @@ type PullRequestReview implements Comment & Deletable & Minimizable & Node & Rea
|
||||
Identifies the primary key from the database.
|
||||
"""
|
||||
databaseId: Int
|
||||
@deprecated(
|
||||
reason: "`databaseId` will be removed because it does not support 64-bit signed integer identifiers. Use `fullDatabaseId` instead. Removal on 2024-07-01 UTC."
|
||||
)
|
||||
|
||||
"""
|
||||
The actor who edited the comment.
|
||||
"""
|
||||
editor: Actor
|
||||
|
||||
"""
|
||||
Identifies the primary key from the database as a BigInt.
|
||||
"""
|
||||
fullDatabaseId: BigInt
|
||||
|
||||
"""
|
||||
The Node ID of the PullRequestReview object
|
||||
"""
|
||||
@@ -36799,6 +36818,9 @@ type PullRequestReviewComment implements Comment & Deletable & Minimizable & Nod
|
||||
Identifies the primary key from the database.
|
||||
"""
|
||||
databaseId: Int
|
||||
@deprecated(
|
||||
reason: "`databaseId` will be removed because it does not support 64-bit signed integer identifiers. Use `fullDatabaseId` instead. Removal on 2024-07-01 UTC."
|
||||
)
|
||||
|
||||
"""
|
||||
The diff hunk to which the comment applies.
|
||||
@@ -36815,6 +36837,11 @@ type PullRequestReviewComment implements Comment & Deletable & Minimizable & Nod
|
||||
"""
|
||||
editor: Actor
|
||||
|
||||
"""
|
||||
Identifies the primary key from the database as a BigInt.
|
||||
"""
|
||||
fullDatabaseId: BigInt
|
||||
|
||||
"""
|
||||
The Node ID of the PullRequestReviewComment object
|
||||
"""
|
||||
|
||||
@@ -30,14 +30,13 @@ adopting_github_actions_for_your_enterprise_ghec:
|
||||
- /actions/security-guides/security-hardening-for-github-actions
|
||||
- >-
|
||||
/billing/managing-billing-for-github-actions/about-billing-for-github-actions
|
||||
adopting_github_actions_for_your_enterprise_ghes_and_ghae:
|
||||
adopting_github_actions_for_your_enterprise_ghes:
|
||||
title: Adopt GitHub Actions for your enterprise
|
||||
description: >-
|
||||
Learn how to plan and implement a rollout of {% data
|
||||
variables.product.prodname_actions %} in your enterprise.
|
||||
versions:
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
guides:
|
||||
- >-
|
||||
/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises
|
||||
|
||||
@@ -1,19 +1,3 @@
|
||||
get_started_with_github_ae:
|
||||
title: Get started with {% data variables.product.prodname_ghe_managed %}
|
||||
description: >-
|
||||
Learn about {% data variables.product.prodname_ghe_managed %} and complete
|
||||
the initial configuration of a new enterprise.
|
||||
versions:
|
||||
ghae: '*'
|
||||
guides:
|
||||
- /admin/overview/about-github-ae
|
||||
- /admin/overview/about-data-residency
|
||||
- /admin/overview/deploying-github-ae
|
||||
- /admin/overview/initializing-github-ae
|
||||
- >-
|
||||
/admin/configuration/hardening-security-for-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list
|
||||
- >-
|
||||
/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae
|
||||
deploy_an_instance:
|
||||
title: Deploy an instance
|
||||
description: >-
|
||||
@@ -71,14 +55,13 @@ adopting_github_actions_for_your_enterprise_ghec:
|
||||
- /actions/security-guides/security-hardening-for-github-actions
|
||||
- >-
|
||||
/billing/managing-billing-for-github-actions/about-billing-for-github-actions
|
||||
adopting_github_actions_for_your_enterprise_ghes_and_ghae:
|
||||
adopting_github_actions_for_your_enterprise_ghes:
|
||||
title: Adopt GitHub Actions for your enterprise
|
||||
description: >-
|
||||
Learn how to plan and implement a rollout of {% data
|
||||
variables.product.prodname_actions %} in your enterprise.
|
||||
versions:
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
guides:
|
||||
- >-
|
||||
/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises
|
||||
|
||||
@@ -1,78 +0,0 @@
|
||||
date: '2021-03-03'
|
||||
sections:
|
||||
features:
|
||||
- heading: 'GitHub Actions beta'
|
||||
notes:
|
||||
- |
|
||||
[{% data variables.product.prodname_actions %}](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. For more information, see "[AUTOTITLE](/actions/learn-github-actions/understanding-github-actions)."
|
||||
|
||||
Please note that when {% data variables.product.prodname_actions %} is enabled during this upgrade, two organizations named "GitHub Actions" (@**actions** and @**github**) will appear in {% data variables.location.product_location %}. These organizations are required by {% data variables.product.prodname_actions %}. Users named @**ghost** and @**actions** appear as the actors for creation of these organizations in the audit log.
|
||||
- heading: 'GitHub Packages beta'
|
||||
notes:
|
||||
- |
|
||||
[{% data variables.product.prodname_registry %}](https://github.com/features/packages) is a package hosting service, natively integrated with {% data variables.product.prodname_actions %}, APIs, and webhooks. Create an [end-to-end DevOps workflow](/github-ae@latest/packages/quickstart) that includes your code, continuous integration, and deployment solutions. During this beta, {% data variables.product.prodname_registry %} is offered free of charge to {% data variables.product.product_name %} customers.
|
||||
- heading: 'GitHub Advanced Security beta'
|
||||
notes:
|
||||
- |
|
||||
{% data variables.product.prodname_GH_advanced_security %} is available in beta and includes both code scanning and secret scanning. During this beta, {% data variables.product.prodname_GH_advanced_security %} features are being offered free of charge to {% data variables.product.product_name %} customers. Repository and organization administrators can opt-in to use {% data variables.product.prodname_GH_advanced_security %} in the Security and Analysis tab under settings.
|
||||
|
||||
Learn more about {% data variables.product.prodname_GH_advanced_security %} [code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) and [secret scanning](/github/administering-a-repository/about-secret-scanning) on {% data variables.product.prodname_ghe_managed %}.
|
||||
|
||||
- heading: Manage teams from your identity provider (IdP)
|
||||
notes:
|
||||
- |
|
||||
Customers using SCIM (System for Cross-domain Identity Management) can now sync security groups in Azure Active Directory with {% data variables.product.company_short %} teams. Once a team has been linked to a security group, membership will be automatically updated in {% data variables.product.product_name %} when a user is added or removed from their assigned security group.
|
||||
|
||||
- heading: IP allow lists beta
|
||||
notes:
|
||||
- |
|
||||
[{% data variables.product.company_short %} IP allow lists](/admin/configuration/restricting-network-traffic-to-your-enterprise) provide the ability to filter traffic from administrator-specified IP ranges, defined by CIDR notation. The allow list is defined at the enterprise or organization account level in Security > Settings. All traffic that attempts to reach resources within the enterprise account and organizations are filtered by the IP allow lists. This functionality is provided in addition to the ability to request network security group changes that filter traffic to the entirety of the GHAE tenant.
|
||||
|
||||
changes:
|
||||
- heading: Developer Changes
|
||||
notes:
|
||||
- |
|
||||
[Organization owners can now disable publication](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization) of {% data variables.product.prodname_pages %} sites from repositories in the organization. This will not unpublish existing sites.
|
||||
- Repositories that use {% data variables.product.prodname_pages %} can now [build and deploy from any branch](/pages/getting-started-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites).
|
||||
- When writing an issue or pull request, the list syntax for bullets, numbers, and tasks will now be autocompleted after you press `return` or `enter`.
|
||||
- You can now delete a directory in a repository from the repository page. When navigating to a directory, a new kebab button next to the "Add file" button gives the option to delete the directory.
|
||||
- It's now easier and faster to [reference issues or pull requests](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#referencing-issues-and-pull-requests), with search across multiple words after the "#".
|
||||
|
||||
- heading: Administration changes
|
||||
notes:
|
||||
- Enterprise owners can now publish a mandatory message. The message is shown to all users and they must acknowledge it. This can be used to display important information, terms of service or policies.
|
||||
- The {% data variables.product.prodname_github_app%} single file path permission can now [support up to ten files](/developers/apps/creating-a-github-app-using-url-parameters).
|
||||
- When configuring a {% data variables.product.prodname_github_app%}, the authorization callback URL is a required field. Now we will permit the integrator to specify multiple callback URLs. {% data variables.product.product_name %} denies authorization if the callback URL from the request is not listed.
|
||||
- A [new API endpoint](/rest/reference/apps#create-a-scoped-access-token) enables the exchange of a user to server token for a user to server token scoped to specific repositories.
|
||||
- Events are now logged in the audit log on [promoting a team member to be a team maintainer and on demoting a team maintainer to be a team member](/admin/user-management/audited-actions#teams).
|
||||
- The [OAuth device authorization flow](/developers/apps/authorizing-oauth-apps#device-flow) is now supported. This allows any CLI client or developer tool to authenticate using a secondary system.
|
||||
- A user can no longer delete their account if SCIM provisioning is enabled.
|
||||
|
||||
- heading: Default branch renaming
|
||||
notes:
|
||||
- |
|
||||
Enterprise and organization owners can now set the default branch name for new repositories. Enterprise owners can also enforce their choice of default branch name across all organizations or allow individual organizations to choose their own.
|
||||
|
||||
Existing repositories are unaffected by these settings, and their default branch name will not be changed.
|
||||
|
||||
This change is one of many changes {% data variables.product.company_short %} is making to support projects and maintainers that want to rename their default branch. To learn more, see [github/renaming](https://github.com/github/renaming).
|
||||
|
||||
bugs:
|
||||
- heading: Bug fixes
|
||||
notes:
|
||||
- Users can no longer set a backup email address on their profile. Their email address is set through the IdP only.
|
||||
- You can no longer enable two-factor authentication after configuring authentication through your IdP.
|
||||
- |
|
||||
{% data variables.product.product_name %} can now connect to Azure Boards.
|
||||
- Version headers were missing from the APIs, and have now been set to "GitHub AE."
|
||||
- Links to documentation have been fixed.
|
||||
- Configuration of audit log forwarding within the enterprise's settings was failing.
|
||||
- Navigating to gists could result in a 500 error.
|
||||
- The Support email or URL was failing to save. It now saves after a period of a few minutes.
|
||||
- Organization level pull request templates were not being applied to all pull requests in the organization.
|
||||
|
||||
known_issues:
|
||||
- heading: Known issues
|
||||
notes:
|
||||
- Geographic location data is not shown in the audit log. Location information can otherwise be discerned from the IP address associated with each event.
|
||||
- The link to {% data variables.product.prodname_registry %} from a repository page shows an incorrect search page when that repository does not have any packages.
|
||||
@@ -1,133 +0,0 @@
|
||||
date: '2021-12-06'
|
||||
sections:
|
||||
features:
|
||||
- heading: 'Administration'
|
||||
notes:
|
||||
- |
|
||||
Customers with active or trial subscriptions for {% data variables.product.product_name %} can now provision {% data variables.product.product_name %} resources from the [Azure Portal](https://portal.azure.com/signin/index/). Your Azure subscription must be feature-flagged to access {% data variables.product.product_name %} resources in the portal. Contact your account manager or {% data variables.contact.contact_enterprise_sales %} to validate your Azure subscription's eligibility. For more information, see "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/deploying-github-ae#deploying-github-ae-with-the-azure-portal)."
|
||||
- heading: 'GitHub Actions'
|
||||
notes:
|
||||
- |
|
||||
[GitHub Actions](https://github.com/features/actions) is now generally available for {% data variables.product.product_name %}. GitHub Actions is a powerful, flexible solution for CI/CD and workflow automation. For more information, see "[AUTOTITLE](/actions/learn-github-actions/understanding-github-actions)."
|
||||
- |
|
||||
Self-hosted runners are the default type of runner system on {% data variables.product.product_name %}, and are now generally available for GitHub Actions. With self-hosted runners, you can manage your own machines or containers for the execution of GitHub Actions jobs. For more information, see "[About self-hosted runners](https://docs.github.com/en/github-ae@latest/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/adding-self-hosted-runners)."
|
||||
- |
|
||||
Environments, environment protection rules, and environment secrets are now generally available for GitHub Actions on {% data variables.product.product_name %}. For more information, see "[AUTOTITLE](/actions/deployment/targeting-different-environments/using-environments-for-deployment)."
|
||||
- |
|
||||
GitHub Actions can now generate a visual graph of your workflow on every run. With workflow visualization, you can achieve the following.
|
||||
|
||||
- View and understand complex workflows.
|
||||
- Track progress of workflows in real-time.
|
||||
- Troubleshoot runs quickly by easily accessing logs and jobs metadata.
|
||||
- Monitor progress of deployment jobs and easily access deployment targets.
|
||||
|
||||
For more information, see "[Using the visualization graph](/actions/managing-workflow-runs/using-the-visualization-graph)."
|
||||
- |
|
||||
GitHub Actions now lets you control the permissions granted to the `GITHUB_TOKEN` secret. The `GITHUB_TOKEN` is an automatically generated secret that lets you make authenticated calls to the API for {% data variables.product.product_name %} in your workflow runs. GitHub Actions generates a new token for each job and expires the token when a job completes. The token has `write` permissions to a number of [API endpoints](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token) except in the case of pull requests from forks, which are always `read`. These new settings allow you to follow a principle of least privilege in your workflows. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)."
|
||||
- |
|
||||
GitHub Actions now supports skipping `push` and `pull_request` workflows by looking for some common keywords in your commit message.
|
||||
- |
|
||||
GitHub CLI 1.9 and later allows you to work with GitHub Actions in your terminal. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-04-15-github-cli-1-9-enables-you-to-work-with-github-actions-from-your-terminal/).
|
||||
|
||||
- heading: 'Code scanning'
|
||||
notes:
|
||||
- |
|
||||
Code scanning is now in beta for {% data variables.product.product_name %}. For more information, see "[About code scanning](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)."
|
||||
- heading: 'Secret scanning'
|
||||
notes:
|
||||
- |
|
||||
You can now specify your own patterns for secret scanning with the beta of custom patterns on {% data variables.product.product_name %}. You can specify patterns for repositories, organizations, and your entire enterprise. When you specify a new pattern, secret scanning searches a repository's entire Git history for the pattern, as well as any new commits. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."
|
||||
- heading: 'GitHub Connect'
|
||||
notes:
|
||||
- |
|
||||
GitHub Connect is now available in beta for {% data variables.product.product_name %}. GitHub Connect brings the power of the world's largest open source community to {% data variables.location.product_location %}. You can allow users to view search results from {% data variables.product.prodname_dotcom_the_website %} on {% data variables.product.product_name %}, show contribution counts from {% data variables.product.product_name %} on {% data variables.product.prodname_dotcom_the_website %}, and use GitHub Actions from {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Managing connections between your enterprise accounts](/admin/configuration/managing-connections-between-your-enterprise-accounts)."
|
||||
- heading: 'GitHub Packages'
|
||||
notes:
|
||||
- |
|
||||
You can now delete any package or package version for GitHub Packages from {% data variables.product.product_name %}'s web UI. You can also undo the deletion of any package or package version within 30 days. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."
|
||||
- |
|
||||
The npm registry for GitHub Packages and {% data variables.product.prodname_dotcom_the_website %} no longer returns a time value in metadata responses, providing substantial performance improvements. {% data variables.product.company_short %} will continue returning the time value in the future.
|
||||
- heading: 'Audit logging'
|
||||
notes:
|
||||
- |
|
||||
Events for pull requests and pull request reviews are now included in the audit log for both [enterprises](/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions) and [organizations](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization). These events help administrators better monitor pull request activity and ensure security and compliance requirements are being met. Events can be viewed from the web UI, exported as CSV or JSON, or accessed via REST API. You can also search the audit log for specific pull request events.
|
||||
- |
|
||||
Additional events for GitHub Actions are now included in the audit log for both [enterprises](/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions) and [organizations](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization).
|
||||
|
||||
- A workflow is deleted or re-run.
|
||||
- A self-hosted runner's version is updated.
|
||||
- heading: 'Authentication'
|
||||
notes:
|
||||
- |
|
||||
GitHub AE now officially supports Okta for SAML single sign-on (SSO) and user provisioning with SCIM. You can also map groups in Okta to teams on GitHub AE. For more information, see "[Configuring authentication and provisioning for your enterprise using Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)" and "[Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)."
|
||||
- |
|
||||
The format of authentication tokens for {% data variables.product.product_name %} has changed. The change affects the format of personal access tokens and access tokens for OAuth Apps, as well as user-to-server, server-to-server, and refresh tokens for GitHub Apps. {% data variables.product.company_short %} recommends updating existing tokens as soon as possible to improve security and allow secret scanning to detect the tokens. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats)" and "[About secret scanning](/code-security/secret-security/about-secret-scanning)."
|
||||
- |
|
||||
You can now authenticate SSH connections to {% data variables.product.product_name %} using a FIDO2 security key by adding an `sk-ecdsa-sha2-nistp256@openssh.com` SSH key to your account. SSH security keys store secret key material on a separate hardware device that requires verification, such as a tap, to operate. Storing the key on separate hardware and requiring physical interaction for your SSH key offers additional security. Since the key is stored on hardware and is non-extractable, the key can't be read or stolen by software running on the computer. The physical interaction prevents unauthorized use of the key since the security key will not operate until you physically interact with it. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)."
|
||||
- |
|
||||
Git Credential Manager (GCM) Core versions 2.0.452 and later now provide secure credential storage and multi-factor authentication support for {% data variables.product.product_name %}. GCM Core with support for {% data variables.product.product_name %} is included with [Git for Windows](https://gitforwindows.org) versions 2.32 and later. GCM Core is not included with Git for macOS or Linux, but can be installed separately. For more information, see the [latest release](https://github.com/microsoft/Git-Credential-Manager-Core/releases/) and [installation instructions](https://github.com/microsoft/Git-Credential-Manager-Core/releases/) in the `microsoft/Git-Credential-Manager-Core` repository.
|
||||
- heading: 'Notifications'
|
||||
notes:
|
||||
- |
|
||||
You can now configure which events you would like to be notified about on {% data variables.product.product_name %}. From any repository, select the {% octicon "file-code" aria-label="The code icon" %} **Watch** drop-down, then click **Custom**. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications)."
|
||||
- heading: 'Issues and pull requests'
|
||||
notes:
|
||||
- |
|
||||
With the [latest version of Octicons](https://github.com/primer/octicons/releases), the states of issues and pull requests are now more visually distinct so you can scan status more easily. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-06-08-new-issue-and-pull-request-state-icons/).
|
||||
- |
|
||||
You can now see all pull request review comments in the **Files** tab for a pull request by selecting the **Conversations** drop-down. You can also require that all pull request review comments are resolved before anyone merges the pull request. For more information, see "[About pull request reviews](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews#discovering-and-navigating-conversations)" and "[About protected branches](/github/administering-a-repository/managing-protected-branches/about-protected-branches#require-conversation-resolution-before-merging)." For more information about management of branch protection settings with the API, see "[Branches](/rest/reference/branches#get-branch-protection)" in the REST API documentation and "[Mutations](/graphql/reference/mutations#createbranchprotectionrule)" in the GraphQL API documentation.
|
||||
- |
|
||||
You can now upload video files everywhere you write Markdown on {% data variables.product.product_name %}. Share demos, show reproduction steps, and more in issue and pull request comments, as well as in Markdown files within repositories, such as READMEs. For more information, see "[Attaching files](/github/writing-on-github/working-with-advanced-formatting/attaching-files)."
|
||||
- |
|
||||
{% data variables.product.product_name %} now shows a confirmation dialog when you request a review from a team with more than 100 members, allowing you to prevent unnecessary notifications for large teams.
|
||||
- |
|
||||
When an issue or pull request has fewer than 30 possible assignees, the assignees control will list all potential users rather than a limited set of suggestions. This behavior helps people in small organizations to quickly find the right user. For more information about assigning users to issues and pull requests, see "[Assigning issues and pull requests to other {% data variables.product.company_short %} users](/issues/tracking-your-work-with-issues/managing-issues/assigning-issues-and-pull-requests-to-other-github-users#assigning-an-individual-issue-or-pull-request)."
|
||||
- |
|
||||
You can now include multiple words after the `#` in a comment for an issue or pull request to further narrow your search. To dismiss the suggestions, press <kbd>Esc</kbd>.
|
||||
- |
|
||||
To prevent the merge of unexpected changes after you enable auto-merge for a pull request, auto-merge is now disabled automatically when new changes are pushed by a user without write access to the repository. Users without write access can still update the pull request with changes from the base branch when auto-merge is enabled. To prevent a malicious user from using a merge conflict to introduce unexpected changes to the pull request, {% data variables.product.product_name %} will disable auto-merge for the pull request if the update causes a merge conflict. For more information about auto-merge, see "[Automatically merging a pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)."
|
||||
- |
|
||||
People with maintain access can now manage the repository-level "Allow auto-merge" setting. This setting, which is off by default, controls whether auto-merge is available on pull requests in the repository. Previously, only people with admin access could manage this setting. Additionally, this setting can now by controlled using the "[Create a repository](/rest/reference/repos#create-an-organization-repository)" and "[Update a repository](/rest/reference/repos#update-a-repository)" REST APIs. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository)."
|
||||
- |
|
||||
The assignees selection for issues and pull requests now supports type ahead searching so you can find users in your organization faster. Additionally, search result rankings have been updated to prefer matches at the start of a person's username or profile name.
|
||||
|
||||
- heading: 'Repositories'
|
||||
notes:
|
||||
- |
|
||||
When viewing the commit history for a file, you can now click {% octicon "file-code" aria-label="The code icon" %} to view the file at the specified time in the repository's history.
|
||||
- |
|
||||
You can now use the web UI to synchronize an out-of-date branch for a fork with the fork's upstream branch. If there are no merge conflicts between the branches, {% data variables.product.product_name %} updates your branch either by fast-forwarding or by merging from upstream. If there are conflicts, {% data variables.product.product_name %} will prompt you to open pull request to resolve the conflicts. For more information, see "[Syncing a fork](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)."
|
||||
- |
|
||||
You can now sort the repositories on a user or organization profile by star count.
|
||||
- |
|
||||
The Repositories REST API's "compare two commits" endpoint, which returns a list of commits reachable from one commit or branch, but unreachable from another, now supports pagination. The API can also now return the results for comparisons over 250 commits. For more information, see the "[Commits](/rest/reference/commits#compare-two-commits)" REST API documentation and "[Traversing with pagination](/rest/guides/traversing-with-pagination)."
|
||||
- |
|
||||
When you define a submodule in {% data variables.location.product_location %} with a relative path, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. Relative paths for repositories with the same owner that follow the pattern <code>../<em>REPOSITORY</em></code> or relative paths for repositories with a different owner that follow the pattern <code>../<em>OWNER</em>/<em>REPOSITORY</em></code> are supported. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}.
|
||||
- |
|
||||
By precomputing checksums, the amount of time a repository is under lock has reduced dramatically, allowing more write operations to succeed immediately and improving monorepo performance.
|
||||
- heading: 'Releases'
|
||||
notes:
|
||||
- |
|
||||
You can now react with emoji to all releases on {% data variables.product.product_name %}. For more information, see "[About releases](/github/administering-a-repository/releasing-projects-on-github/about-releases)."
|
||||
- heading: 'Themes'
|
||||
notes:
|
||||
- |
|
||||
Dark and dark dimmed themes are now available for the web UI. {% data variables.product.product_name %} will match your system preferences when you haven't set theme preferences in {% data variables.product.product_name %}. You can also customize the themes that are active during day and night. For more information, see "[Managing your theme settings](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)."
|
||||
- heading: 'Markdown'
|
||||
notes:
|
||||
- |
|
||||
Markdown files in your repositories now automatically generate a table of contents in the header the file has two or more headings. The table of contents is interactive and links to the corresponding section. All six Markdown heading levels are supported. For more information, see "[About READMEs](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-readmes#auto-generated-table-of-contents-for-readme-files)."
|
||||
- |
|
||||
`code` markup is now supported in titles for issues and pull requests. Text within backticks (`` ` ``) will appear rendered in a fixed-width font anywhere the issue or pull request title appears in the web UI for {% data variables.product.product_name %}.
|
||||
- |
|
||||
While editing Markdown in files, issues, pull requests, or comments, you can now use a keyboard shortcut to insert a code block. The keyboard shortcut is <kbd>command</kbd> + <kbd>E</kbd> on a Mac or <kbd>Ctrl</kbd> + <kbd>E</kbd> on other devices. For more information, see "[Basic writing and formatting syntax](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#quoting-code)."
|
||||
- |
|
||||
You can append `?plain=1` to the URL for any Markdown file to display the file without rendering and with line numbers. You can use the plain view to link other users to specific lines. For example, appending `?plain=1#L52` will highlight line 52 of a plain text Markdown file. For more information, "[Creating a permanent link to a code snippet](/github/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet#linking-to-markdown)."
|
||||
- heading: 'GitHub Apps'
|
||||
notes:
|
||||
- |
|
||||
API requests to create an installation access token now respect IP allow lists for an enterprise or organization. Any API requests made with an installation access token for a GitHub App installed on your organization already respect IP allow lists. This feature does not currently consider any Azure network security group (NSG) rules that {% data variables.product.company_short %} Support has configured for {% data variables.location.product_location %}. For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise#about-ip-allow-lists)," "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)," and "[Apps](https://docs.github.com/en/rest/reference/apps#create-an-installation-access-token-for-an-app)" in the REST API documentation.
|
||||
- heading: 'Webhooks'
|
||||
notes:
|
||||
- |
|
||||
You can now programmatically resend or check the status of webhooks through the REST API. For more information, see "[Repositories](https://docs.github.com/en/rest/reference/repos#webhooks)," "[Organizations](https://docs.github.com/en/rest/reference/orgs#webhooks)," and "[Apps](https://docs.github.com/en/rest/reference/apps#webhooks)" in the REST API documentation.
|
||||
@@ -1,200 +0,0 @@
|
||||
date: '2022-05-17'
|
||||
sections:
|
||||
features:
|
||||
- heading: 'GitHub Advanced Security features are generally available'
|
||||
notes:
|
||||
- |
|
||||
Code scanning and secret scanning are now generally available for GitHub AE. For more information, see "[AUTOTITLE](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[AUTOTITLE](/code-security/secret-scanning/about-secret-scanning)."
|
||||
- |
|
||||
Custom patterns for secret scanning is now generally available. For more information, see "[AUTOTITLE](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."
|
||||
|
||||
- heading: 'View all code scanning alerts for a pull request'
|
||||
notes:
|
||||
- |
|
||||
You can now find all code scanning alerts associated with your pull request with the new pull request filter on the code scanning alerts page. The pull request checks page shows the alerts introduced in a pull request, but not existing alerts on the pull request branch. The new "View all branch alerts" link on the Checks page takes you to the code scanning alerts page with the specific pull request filter already applied, so you can see all the alerts associated with your pull request. This can be useful to manage lots of alerts, and to see more detailed information for individual alerts. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-code-scanning-alerts)."
|
||||
|
||||
- heading: 'Security overview for organizations'
|
||||
notes:
|
||||
- |
|
||||
GitHub Advanced Security now offers an organization-level view of the application security risks detected by code scanning, Dependabot, and secret scanning. The security overview shows the enablement status of security features on each repository, as well as the number of alerts detected.
|
||||
|
||||
In addition, the security overview lists all secret scanning alerts at the organization level. Similar views for Dependabot and code scanning alerts are coming in future releases. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
|
||||
|
||||
|
||||
|
||||
- heading: 'Dependency graph'
|
||||
notes:
|
||||
- |
|
||||
Dependency graph is now available on GitHub AE. The dependency graph helps you understand the open source software that you depend on by parsing the dependency manifests checked into repositories. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)."
|
||||
|
||||
- heading: 'Dependabot alerts'
|
||||
notes:
|
||||
- |
|
||||
Dependabot alerts can now notify you of vulnerabilities in your dependencies on GitHub AE. You can enable Dependabot alerts by enabling the dependency graph, enabling GitHub Connect, and syncing vulnerabilities from the GitHub Advisory Database. This feature is in beta and subject to change. For more information, see "[About Dependabot alerts](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)."
|
||||
|
||||
After you enable Dependabot alerts, members of your organization will receive notifications any time a new vulnerability that affects their dependencies is added to the GitHub Advisory Database or a vulnerable dependency is added to their manifest. Members can customize notification settings. For more information, see "[Configuring notifications for % data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)."
|
||||
|
||||
- heading: 'Security manager role for organizations'
|
||||
notes:
|
||||
- |
|
||||
Organizations can now grant teams permission to manage security alerts and settings on all their repositories. The "security manager" role can be applied to any team and grants the team's members the following permissions.
|
||||
|
||||
- Read access on all repositories in the organization
|
||||
- Write access on all security alerts in the organization
|
||||
- Access to the organization-level security tab
|
||||
- Write access on security settings at the organization level
|
||||
- Write access on security settings at the repository level
|
||||
|
||||
For more information, see "[Managing security managers in your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)."
|
||||
|
||||
- heading: 'Ephemeral runners and autoscaling webhooks for GitHub Actions'
|
||||
notes:
|
||||
- |
|
||||
GitHub AE now supports ephemeral (single job) self-hosted runners and a new [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook to make autoscaling runners easier.
|
||||
|
||||
Ephemeral runners are good for self-managed environments where each job is required to run on a clean image. After a job is run, GitHub AE automatically unregisteres ephemeral runners, allowing you to perform any post-job management.
|
||||
|
||||
You can combine ephemeral runners with the new `workflow_job` webhook to automatically scale self-hosted runners in response to job requests from GitHub Actions.
|
||||
|
||||
For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)."
|
||||
|
||||
- heading: 'Composite actions for GitHub Actions'
|
||||
notes:
|
||||
- |
|
||||
You can reduce duplication in your workflows by using composition to reference other actions. Previously, actions written in YAML could only use scripts. For more information, see "[Creating a composite action](/actions/creating-actions/creating-a-composite-action)."
|
||||
|
||||
- heading: 'New token scope for management of self-hosted runners'
|
||||
notes:
|
||||
- |
|
||||
Managing self-hosted runners at the enterprise level no longer requires using personal access tokens with the `admin:enterprise` scope. You can instead use the `new manage_runners:enterprise` scope to restrict the permissions on your tokens. Tokens with this scope can authenticate to many REST API endpoints to manage your enterprise's self-hosted runners.
|
||||
|
||||
- heading: 'Audit log accessible via REST API'
|
||||
notes:
|
||||
- |
|
||||
You can now use the REST API to programmatically interface with the audit log. While audit log forwarding provides you with the ability to retain and analyze data with your own toolkit and determine patterns over time, the new REST API will help you perform limited analysis on events of note that have happened in recent history. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#using-the-rest-api)."
|
||||
|
||||
- heading: 'Expiration dates for personal access tokens'
|
||||
notes:
|
||||
- |
|
||||
You can now set an expiration date on new and existing personal access tokens. GitHub AE will send you an email when it's time to renew a token that's about to expire. Tokens that have expired can be regenerated, giving you a duplicate token with the same properties as the original. When using a token with the GitHub AE API, you'll see a new header, `GitHub-Authentication-Token-Expiration`, indicating the token's expiration date. You can use this in scripts, for example to log a warning message as the expiration date approaches. For more information, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)" and "[Getting started with the REST API](/rest/guides/getting-started-with-the-rest-api#using-personal-access-tokens)."
|
||||
|
||||
- heading: 'Export a list of people with access to a repository'
|
||||
notes:
|
||||
- |
|
||||
Organization owners can now export a list of the people with access to a repository in CSV format. For more information, see "[Viewing people with access to your repository](/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository#exporting-a-list-of-people-with-access-to-your-repository)."
|
||||
|
||||
- heading: 'Improved management of code review assignments'
|
||||
notes:
|
||||
- |
|
||||
New settings to manage code review assignment code review assignment help distribute a team's pull request review across the team members so reviews aren't the responsibility of just one or two team members.
|
||||
|
||||
- Child team members: Limit assignment to only direct members of the team. Previously, team review requests could be assigned to direct members of the team or members of child teams.
|
||||
- Count existing requests: Continue with automatic assignment even if one or more members of the team are already requested. Previously, a team member who was already requested would be counted as one of the team's automatic review requests.
|
||||
- Team review request: Keep a team assigned to review even if one or more members is newly assigned.
|
||||
|
||||
For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."
|
||||
|
||||
- heading: 'New themes'
|
||||
notes:
|
||||
- |
|
||||
Two new themes are available for the GitHub AE web UI.
|
||||
|
||||
- A dark high contrast theme, with greater contrast between foreground and background elements
|
||||
- Light and dark colorblind, which swap colors such as red and green for orange and blue
|
||||
|
||||
For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)."
|
||||
|
||||
- heading: 'Markdown improvements'
|
||||
notes:
|
||||
- |
|
||||
You can now use footnote syntax in any Markdown field to reference relevant information without disrupting the flow of your prose. Footnotes are displayed as superscript links. Click a footnote to jump to the reference, displayed in a new section at the bottom of the document. For more information, see "[Basic writing and formatting syntax](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#footnotes)."
|
||||
|
||||
- |
|
||||
You can now toggle between the source view and rendered Markdown view through the web UI by clicking the {% octicon "code" aria-label="The Code icon" %} button to "Display the source diff" at the top of any Markdown file. Previously, you needed to use the blame view to link to specific line numbers in the source of a Markdown file.
|
||||
|
||||
- |
|
||||
GitHub AE now automatically generates a table of contents for Wikis, based on headings.
|
||||
|
||||
changes:
|
||||
- heading: 'Performance'
|
||||
notes:
|
||||
- |
|
||||
Page loads and jobs are now significantly faster for repositories with many Git refs.
|
||||
|
||||
- heading: 'Administration'
|
||||
notes:
|
||||
- |
|
||||
The user impersonation process is improved. An impersonation session now requires a justification for the impersonation, actions are recorded in the audit log as being performed as an impersonated user, and the user who is impersonated will receive an email notification that they have been impersonated by an enterprise owner. For more information, see "[Impersonating a user](/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user)."
|
||||
|
||||
- heading: 'GitHub Actions'
|
||||
notes:
|
||||
- |
|
||||
To mitigate insider man-in-the-middle attacks when using actions resolved through GitHub Connect to GitHub.com from GitHub AE, GitHub AE retires the actions namespace (`OWNER/NAME`) on use. Retiring the namespace prevents that namespace from being created in your enterprise, and ensures all workflows referencing the action will download it from GitHub.com. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)."
|
||||
|
||||
- |
|
||||
The audit log now includes additional events for GitHub Actions. GitHub AE now records audit log entries for the following events.
|
||||
|
||||
- A self-hosted runner is registered or removed.
|
||||
- A self-hosted runner is added to a runner group, or removed from a runner group.
|
||||
- A runner group is created or removed.
|
||||
- A workflow run is created or completed.
|
||||
- A workflow job is prepared. Importantly, this log includes the list of secrets that were provided to the runner.
|
||||
|
||||
For more information, see "[Security hardening for GitHub Actions](/actions/security-guides/security-hardening-for-github-actions)."
|
||||
|
||||
- heading: 'GitHub Advanced Security'
|
||||
notes:
|
||||
- |
|
||||
Code scanning will now map alerts identified in `on:push` workflows to show up on pull requests, when possible. The alerts shown on the pull request are those identified by comparing the existing analysis of the head of the branch to the analysis for the target branch that you are merging against. Note that if the pull request's merge commit is not used, alerts can be less accurate when compared to the approach that uses `on:pull_request` triggers. For more information, see "[About code scanning with CodeQL](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)."
|
||||
|
||||
Some other CI/CD systems can exclusively be configured to trigger a pipeline when code is pushed to a branch, or even exclusively for every commit. Whenever such an analysis pipeline is triggered and results are uploaded to the SARIF API, code scanning will try to match the analysis results to an open pull request. If an open pull request is found, the results will be published as described above. For more information, see "[Uploading a SARIF file to GitHub](/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github)."
|
||||
|
||||
- |
|
||||
GitHub AE now detects secrets from additional providers. For more information, see "[Secret scanning patterns](/code-security/secret-scanning/secret-scanning-patterns#supported-secrets)."
|
||||
|
||||
- heading: 'Pull requests'
|
||||
notes:
|
||||
- |
|
||||
The timeline and Reviewers sidebar on the pull request page now indicate if a review request was automatically assigned to one or more team members because that team uses code review assignment.
|
||||
|
||||
|
||||
|
||||
- |
|
||||
You can now filter pull request searches to only include pull requests you are directly requested to review by choosing **Awaiting review from you**. For more information, see "[Searching issues and pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests)."
|
||||
|
||||
- |
|
||||
If you specify the exact name of a branch when using the branch selector menu, the result now appears at the top of the list of matching branches. Previously, exact branch name matches could appear at the bottom of the list.
|
||||
|
||||
- |
|
||||
When viewing a branch that has a corresponding open pull request, GitHub AE now links directly to the pull request. Previously, there would be a prompt to contribute using branch comparison or to open a new pull request.
|
||||
|
||||
- |
|
||||
You can now click a button to copy the full raw contents of a file to the clipboard. Previously, you would need to open the raw file, select all, and then copy. To copy the contents of a file, navigate to the file and click in the toolbar. Note that this feature is currently only available in some browsers.
|
||||
|
||||
- |
|
||||
A warning is now displayed when viewing a file that contains bidirectional Unicode text. Bidirectional Unicode text can be interpreted or compiled differently than it appears in a user interface. For example, hidden bidirectional Unicode characters can be used to swap segments of text in a file. For more information about replacing these characters, see the [GitHub Changelog](https://github.blog/changelog/2021-10-31-warning-about-bidirectional-unicode-text/).
|
||||
|
||||
- heading: 'Repositories'
|
||||
notes:
|
||||
- |
|
||||
GitHub AE now includes enhanced support for _CITATION.cff_ files. _CITATION.cff_ files are plain text files with human- and machine-readable citation information. GitHub AE parses this information into convenient formats such as [APA](https://apastyle.apa.org) and [BibTeX](https://en.wikipedia.org/wiki/BibTeX) that can be copied by others. For more information, see "[About CITATION files](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)."
|
||||
|
||||
- |
|
||||
You can now add, delete, or view autolinks through the Repositories API's Autolinks endpoint. For more information, see "[Autolinked references and URLs](/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls)" and "[Repositories](/rest/reference/repos#autolinks)" in the REST API documentation.
|
||||
|
||||
- heading: 'Releases'
|
||||
notes:
|
||||
|
||||
- |
|
||||
The tag selection component for GitHub releases is now a drop-down menu rather than a text field. For more information, see "[Managing releases in a repository](/repositories/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)."
|
||||
|
||||
- heading: 'Markdown'
|
||||
notes:
|
||||
|
||||
- |
|
||||
When dragging and dropping files such as images and videos into a Markdown editor, GitHub AE now uses the mouse pointer location instead of the cursor location when placing the file.
|
||||
|
||||
- heading: 'REST API'
|
||||
notes:
|
||||
- |
|
||||
REST API previews have now graduated and are an official part of the API. Preview headers are no longer required for REST API endpoints, but will still function as expected if you continue to specify a graduated preview in the `Accept` header of a request.
|
||||
@@ -1,164 +0,0 @@
|
||||
date: '2022-10-25'
|
||||
sections:
|
||||
features:
|
||||
- heading: 'Security & access management'
|
||||
notes:
|
||||
- |
|
||||
Users with admin access to a repository can better understand who has access to the repository, see what level of access each user has, and more easily manage access to the repository. For example, users can accomplish the following tasks.
|
||||
|
||||
- Search all members, teams, and collaborators who have access to the repository.
|
||||
- View when members have mixed role assignments, granted to them directly as individuals or indirectly via a team: a new "mixed roles" warning displays the highest level role the user is granted if their access is higher than their assigned role.
|
||||
|
||||
For more information, see "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)."
|
||||
|
||||
- heading: 'Administration'
|
||||
notes:
|
||||
- |
|
||||
Enterprise owners can now show additional links to enterprise members and collaborators in a custom footer. For more information, see "[Configuring custom footers](/admin/configuration/configuring-your-enterprise/configuring-custom-footers)."
|
||||
|
||||
- heading: 'GitHub Actions'
|
||||
notes:
|
||||
- |
|
||||
Users can reuse a workflow with a single line of configuration. Reusable workflows save time and maintenance by removing the need to copy and paste workflow definitions across repositories. Reusable workflows are in beta and subject to change. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows)."
|
||||
- |
|
||||
The updated management experience for self-hosted runners simplifies management of runner groups and provides an improved overview of your runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)."
|
||||
- |
|
||||
Dependabot now shares secrets with GitHub Actions when Dependabot triggers a workflow run, so users can now pull from private package registries within CI pipelines using Dependabot's secrets. For more information, see "[Managing encrypted secrets for Dependabot](/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot)."
|
||||
- |
|
||||
Users can use an `if` conditional to prevent specific steps in a composite action from executing unless a condition is met. Like steps defined in workflows, you can use any supported context and expression to create a conditional. For more information about composite actions, see "[Creating a composite action](/actions/creating-actions/creating-a-composite-action)."
|
||||
- |
|
||||
Users can provide a better experience to users of a workflow by specifying input types for manually triggered workflows. Workflows now support `choice`, `boolean`, and `environment`. For more information, see "[Workflow syntax for GitHub Actions](/actions/using-workflows/workflow-syntax-for-github-actions#onworkflow_dispatchinputs)."
|
||||
- |
|
||||
The first available matching runner at the repository, organization, or enterprise level will run each job in all cases, which means jobs are sent to self-hosted runners much faster, especially for organizations and enterprises with many self-hosted runners. Previously, when running a job that required a self-hosted runner, GitHub Actions would look for self-hosted runners in the repository, organization, and enterprise, in that order. For more information, see "[Using self-hosted runners in a workflow](/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow)."
|
||||
- |
|
||||
Users can specify that a JavaScript action should run in Node.js 16 by specifying `runs.using` as `node16`. Node.js 16 support supplements the existing support for Node.js 12. Runners must have version 2.285.0 or later of the GitHub Actions Runner installed. For more information, see "[Metadata syntax for GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-javascript-actions)" and the [`actions/runner` repository](https://github.com/actions/runner).
|
||||
- |
|
||||
Users can add, list, and remove labels for self-hosted runners using the REST API. For more information, see "[Self-hosted runners](/rest/actions/self-hosted-runners)" in the REST API documentation.
|
||||
|
||||
- heading: 'GitHub Advanced Security'
|
||||
notes:
|
||||
- |
|
||||
Users can improve the security of services and tools created with Ruby using CodeQL code scanning. For all common Ruby versions up to and including 3.02, CodeQL can detect common issues such as SQL injection, ReDoS, OS command and argument injection, XML entity expansion, reflected cross-site scripting (XSS), stored XSS, unsafe deserialization, and hard-coded credentials. To enable Ruby analysis, users must update an existing CodeQL code scanning workflow file. Ruby support for CodeQL is in beta and subject to change. For more information, see "[Configuring code scanning](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#changing-the-languages-that-are-analyzed)" and the [CodeQL documentation](https://codeql.github.com/docs/codeql-language-guides/codeql-for-ruby). For more information about code scanning with CodeQL, see "[About code scanning with CodeQL](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)."
|
||||
- |
|
||||
CodeQL's Python analysis supports additional frameworks and can detect more potential sources of untrusted user data, steps through which that data flows, and potentially dangerous sinks in which this data could end up. For more information, see "[Supported languages and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/#python-built-in-support)" in the CodeQL documentation.
|
||||
- |
|
||||
Users can retrieve commit details of secrets detected in private repository scans using the REST API. The new endpoint will surface details of a secret's first detection within a file, including the secret's location and commit SHA. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning)" and "[Secret scanning](/rest/secret-scanning)" in the REST API documentation.
|
||||
- |
|
||||
The code scanning API includes the following improvements.
|
||||
|
||||
- Alerts include the `fixed_at` timestamp, which is the first time that the alert was not detected in an analysis. Users can use this data to better understand when code scanning alerts are being fixed.
|
||||
- Users can sort for the most important alert results using `sort` and `direction` on either `created`, `updated`, or `number`. For more information, see [Code scanning](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository) in the REST API documentation.
|
||||
- The alerts and alert endpoint response include a `Last-Modified` header. For more information, see [`Last-Modified`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Last-Modified) in the Mozilla documentation.
|
||||
- SARIF responses for code scanning analyses include `relatedLocations`, which may contain locations which are not the primary location of the alert. For an example, see the [SARIF spec](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012616). For more information, see [Code scanning](/rest/code-scanning#get-a-code-scanning-analysis-for-a-repository) in the REST API documentation.
|
||||
- The webhook response alert rule object includes `help` and `tags` data. For more information, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#code_scanning_alert)."
|
||||
- |
|
||||
Organization owners and security managers can retrieve private repositories' secret scanning results at the enterprise level using the REST API. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-private-repositories)" and "[Secret scanning](/rest/reference/secret-scanning)" in the REST API documentation.
|
||||
|
||||
- heading: 'Dependabot'
|
||||
notes:
|
||||
- |
|
||||
Users can dismiss Dependabot alerts via the GraphQL API. For more information, see "[Mutations](/graphql/reference/mutations#dismissrepositoryvulnerabilityalert)" in the GraphQL API documentation.
|
||||
|
||||
- heading: 'Code security'
|
||||
notes:
|
||||
- |
|
||||
Dependency graph detects Python dependencies in repositories that use the Poetry package manager. Dependencies will be detected from both `pyproject.toml` and `poetry.lock` manifest files. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)."
|
||||
- |
|
||||
Developers and security researchers can use CodeQL to build databases and analyze code on machines powered by Apple silicon chips, such as the M1. Both the [CodeQL CLI](https://codeql.github.com/docs/codeql-overview/about-codeql/) and [VS Code extension](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-codeql) support Apple silicon. To use the CodeQL CLI or the VS Code extension on Apple silicon, users must install the [Xcode command-line developer tools](https://developer.apple.com/downloads/index.action) and [Rosetta 2](https://support.apple.com/en-us/HT211861). CodeQL support for Apple silicon is in beta and subject to change.
|
||||
|
||||
- For more information about configuration of the CodeQL CLI on supported platforms, see "[Using the CodeQL CLI](https://codeql.github.com/docs/codeql-cli/using-the-codeql-cli/#using-the-codeql-cli)" in the CodeQL documentation.
|
||||
- For more information about CodeQL, see "[About CodeQL](https://codeql.github.com/docs/codeql-overview/about-codeql/)" in the CodeQL documentation and "[About code scanning](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)."
|
||||
- |
|
||||
Users of the CodeQL CLI versions 2.7.1 and later can include query help in SARIF files as Markdown, and the help text will appear in GitHub AE's code scanning UI. Users can include query help as a Markdown file with the same name as the corresponding query file. For example, if your query file is `MyCustomQuery.ql`, the name of the query help file would be `MyCustomQuery.md`. For more information about authorship of query help for custom CodeQL queries, see the [query help style guide](https://github.com/github/codeql/blob/main/docs/query-help-style-guide.md).
|
||||
- Users who don't use GitHub Actions for CI/CD and code scanning must specify the addition of query help when running the `codeql database analyze` command by including the `--sarif-add-query-help` flag. For more information, see "[Analyzing databases with the CodeQL CLI](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/#including-query-help-for-custom-codeql-queries-in-sarif-files)" in the CodeQL documentation.
|
||||
|
||||
- heading: 'Notifications'
|
||||
notes:
|
||||
- |
|
||||
Users can unsubscribe from all repositories owned by a given user or organization. For more information, see "[Managing your subscriptions](/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions#unwatching-repositories)."
|
||||
- |
|
||||
Organization owners can unsubscribe from email notifications when new deploy keys are added to repositories belonging to their organizations. For more information, see "[Configuring notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#organization-alerts-notification-options)."
|
||||
- |
|
||||
The subject line for email notifications for issues and pull requests includes "(Issue #_NUMBER_)" or "(PR #_NUMBER_)" to help users easily distinguish between the two notification types.
|
||||
- |
|
||||
The **View on GitHub** link at the bottom of email notifications is no longer hidden by default in Gmail.
|
||||
|
||||
- heading: 'Organizations'
|
||||
notes:
|
||||
- |
|
||||
Organization members can now view a list of enterprise owners. Whenever an organization member encounters a prompt to contact an enterprise owner, a link will direct the user to the list. The list is also accessible using the GraphQL API's `Organization` object at the `enterpriseOwners` endpoint. For more information, see "[Viewing people's roles in an organization](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization#view-enterprise-owners-and-their-roles-in-an-organization)."
|
||||
|
||||
- heading: 'Repositories'
|
||||
notes:
|
||||
- |
|
||||
Users with admin access to a repository can rename branches that are protected by branch protection rules. For more information, see "[Renaming a branch](/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule)."
|
||||
- |
|
||||
Instead of allowing all or no users to force push, people with admin access to a repository can choose who can force push to the repository. For more information, see "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#allow-force-pushes)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule)."
|
||||
- |
|
||||
Users with admin access to a repository can require that all changes to a protected branch are made using a pull request, but without requiring reviews. For more information, see "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#require-pull-request-reviews-before-merging)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule)."
|
||||
- |
|
||||
Users with admin access to a repository can allow specific users and teams to bypass pull request requirements. For more information, see "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule)."
|
||||
- |
|
||||
Users can use single-character prefixes for custom autolinks. Autolink prefixes also allow `.`, `-`, `_`, `+`, `=`, `:`, `/`, and `#` characters, as well as alphanumerics. For more information, see "[Configuring autolinks to reference external resources](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources)."
|
||||
|
||||
- heading: 'Pull requests'
|
||||
notes:
|
||||
- |
|
||||
Users can enable **Only notify requested team members** independently of **Enable auto assignment** in the team's code review settings, allowing users to require the team for review, but without always notifying the whole team unnecessarily. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."
|
||||
|
||||
- heading: 'Releases'
|
||||
notes:
|
||||
- |
|
||||
The releases UI is improved, providing clarity into what's included in a given release and recognition for contributors to the release. Pagination is improved, and new search functionality is available.
|
||||
- |
|
||||
Users can automatically generate release notes that include a summary of all the pull requests for a given release. For more information, see "[Automatically generated release notes](/repositories/releasing-projects-on-github/automatically-generated-release-notes)."
|
||||
|
||||
- heading: 'Gists'
|
||||
notes:
|
||||
- |
|
||||
Users can preview renderings of Markdown files in gists. When creating or editing a gist file with the Markdown file extension, `.md`, a **Preview** or **Preview changes** tab will display a Markdown rendering of the file's contents. For more information about gists, see "[Editing and sharing content with gists](/get-started/writing-on-github/editing-and-sharing-content-with-gists)."
|
||||
|
||||
- heading: 'Markdown'
|
||||
notes:
|
||||
- |
|
||||
Users can choose to use a fixed-width font in Markdown fields, like comments on issues and pull requests. For more information, see "[About writing and formatting on GitHub](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github#enabling-fixed-width-fonts-in-the-editor)."
|
||||
- |
|
||||
Users can specify the theme an image is displayed for in Markdown. For more information, see "[Basic writing and formatting syntax](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#specifying-the-theme-an-image-is-shown-to)."
|
||||
- |
|
||||
Users can quickly create a Markdown link while editing text in Markdown-enabled fields like issue or pull request comments by selecting text and then pasting a URL.
|
||||
- |
|
||||
HTML links that users paste into Markdown fields are automatically converted into Markdown links. To paste HTML links as plain text, press <kbd>⌘</kbd>/<kbd>ctrl</kbd> + <kbd>shift</kbd> + <kbd>v</kbd>.
|
||||
- |
|
||||
Right-to-left languages are supported natively in Markdown files and comments in issues, pull requests, and discussions.
|
||||
|
||||
- heading: 'Developer experience'
|
||||
notes:
|
||||
- |
|
||||
Users can set a preferred tab size. All code on GitHub AE with tabs will render using the preferred tab size. For more information, see "[Managing your tab size rendering preference](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-tab-size-rendering-preference)."
|
||||
|
||||
- heading: 'Accessibility'
|
||||
notes:
|
||||
- |
|
||||
Users can manage keyboard shortcuts with GitHub AE's new accessibility settings, and can choose to disable character key shortcuts that only use single characters, such as <kbd>s</kbd>, <kbd>g c</kbd>, and <kbd>.</kbd> (the period key). For more information, see "[Managing accessibility settings](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings#managing-motion)."
|
||||
|
||||
- heading: 'GitHub Apps'
|
||||
notes:
|
||||
- |
|
||||
To ensures all changes are validated by the intended app, users can now control which GitHub App a required status check is provided by. If status is then provided by a different app or by a user via a commit status, merging will be prevented. Existing required status checks will continue to accept status from any app, but can be updated to only accept status from a specific app. Newly-added required status checks will default to the app that most recently reported the status, but you can choose a different app or allow any app to provide the status. For more information, see "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#require-status-checks-before-merging)" and "[Editing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule#editing-a-branch-protection-rule)."
|
||||
|
||||
- heading: 'Webhooks'
|
||||
notes:
|
||||
- |
|
||||
Organization owners and users with admin access to a repository can trigger webhooks to listen for changes to branch protection rules. For more information, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#branch_protection_rule)."
|
||||
|
||||
changes:
|
||||
- When users are invited to a private repository, navigating to the private repository's URL will display a prompt to join the repository instead of a `404` error.
|
||||
- Invitations to private repositories appear in notifications.
|
||||
- When a user types `@` in the web UI to mention a user, the list ranks participants in issues, pull requests, and discussions higher so that it's more likely the person a user is looking for will be listed first.
|
||||
- To prevent potentially malicious code from executing in a privileged workflow, the following changes apply to GitHub Actions workflows triggered by Dependabot.
|
||||
|
||||
- Workflow runs triggered for the `create`, `deployment`, and `deployment_status` events will always receive a read-only token and no secrets.
|
||||
- Workflow runs triggered for the `pull_request_target` event on pull requests where the base ref was created by Dependabot will always receive a read-only token and no secrets.
|
||||
- Workflow runs on `push` and `pull_request` events triggered by Dependabot respect the `permissions` specified in your workflows. The default token permissions will remain read-only.
|
||||
- The setting to hide whitespace changes in a pull request's **Files changed** tab is preserved for each pull request.
|
||||
- The "Update a pull request branch" API for GitHub Apps now requires the calling user or application to have write access to the head repository. If the caller does not have write access, the API will return a `403 Forbidden` response. For more information, see "[Pulls](https://docs.github.com/rest/pulls/pulls#update-a-pull-request-branch)" in the REST API documentation.
|
||||
@@ -1,302 +0,0 @@
|
||||
date: '2023-02-16'
|
||||
sections:
|
||||
features:
|
||||
- heading: 'Administrator experience'
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/2351
|
||||
- |
|
||||
Enterprise owners can join organizations on GitHub AE as a member or owner from the enterprise account's **Organizations** page. For more information, see "[Managing your role in an organization owned by your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise)."
|
||||
|
||||
- heading: 'Identity and access management'
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/1945
|
||||
- |
|
||||
Custom repository roles are generally available. With custom repository roles, organization owners now have more granular control over the repository access permissions they can grant to users. Custom repository roles are also fully supported by the REST API. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)" and "[Organizations](/rest/reference/orgs#list-custom-repository-roles-in-an-organization)" in the REST API documentation.
|
||||
|
||||
- heading: 'Policies'
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/2073
|
||||
- |
|
||||
Enterprise owners can prevent organization owners from inviting collaborators to GitHub AE repositories. For more information, see "[Enforcing a policy for inviting collaborators to repositories](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-collaborators-to-repositories)."
|
||||
|
||||
- heading: 'GitHub Advanced Security'
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/2321
|
||||
- |
|
||||
Users can opt to receive a webhook event that triggers when someone enables or disables a code security or analysis feature for an organization or repository. For more information, see the following documentation.
|
||||
|
||||
- "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#security_and_analysis)" in the webhook documentation
|
||||
- "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)"
|
||||
- "[Managing security and analysis features for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)"
|
||||
# https://github.com/github/releases/issues/2318, https://github.com/github/releases/issues/2277
|
||||
- |
|
||||
Enterprise owners and users can view secret scanning alerts and bypasses of secret scanning's push protection in the enterprise and organization audit logs, and via the REST API. For more information, see the following documentation.
|
||||
|
||||
- "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)"
|
||||
- "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#secret_scanning_push_protection-category-actions)"
|
||||
- "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#secret_scanning_push_protection-category-actions)"
|
||||
- "[Secret Scanning](/rest/secret-scanning#list-secret-scanning-alerts-for-an-enterprise)" in the REST API documentation
|
||||
# https://github.com/github/releases/issues/1909
|
||||
- |
|
||||
Organization owners can now configure two new permissions for secret scanning when managing custom repository roles.
|
||||
|
||||
- View secret scanning results
|
||||
- Dismiss or reopen secret scanning results
|
||||
|
||||
For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."
|
||||
# https://github.com/github/releases/issues/1703, https://github.com/github/releases/issues/2084
|
||||
- |
|
||||
Users can execute a dry run of custom secret scanning patterns at the enterprise, organization, or repository level, depending on their access. Dry runs allow users to review and hone their patterns before publishing them and generating alerts. You can compose a pattern, then use **Save and dry run** to retrieve results. The scans typically take just a few seconds, but GitHub AE will also notify users via email when dry run results are ready. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-private-repositories)" and "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."
|
||||
# https://github.com/github/releases/issues/2076
|
||||
- |
|
||||
Users can enable secret scanning for archived repositories using the UI or API. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-private-repositories)," "[About archived repositories](/repositories/archiving-a-github-repository/archiving-repositories)," and "[Repositories](/rest/repos/repos#update-a-repository)" in the REST API documentation.
|
||||
# https://github.com/github/releases/issues/2228
|
||||
- |
|
||||
Secret scanning prevents the leak of secrets in the web editor. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#using-secret-scanning-as-a-push-protection-from-the-web-ui)."
|
||||
# https://github.com/github/releases/issues/2097
|
||||
- |
|
||||
Code scanning now detects a larger number of CWEs, and CodeQL code scanning fully supports the standard language features in the following language releases.
|
||||
|
||||
- C# 10 / .NET 6
|
||||
- Python 3.10
|
||||
- Java 17
|
||||
- TypeScript 4.5
|
||||
|
||||
For more information, see the [GitHub Blog](https://github.blog/changelog/2022-02-25-code-scanning-detects-more-security-issues-supports-new-language-versions/).
|
||||
# https://github.com/github/releases/issues/1792
|
||||
- |
|
||||
Organization owners and security managers can view code scanning alerts in an organization's **Security** tab. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
|
||||
# https://github.com/github/releases/issues/2049
|
||||
- |
|
||||
The code scanning alert page now always shows the alert status and information for the default branch. There is a new "Affected branches" panel in the sidebar where you can see the status of the alert in other branches. If the alert does not exist in your default branch, the alert page will show the status as "In branch" or "In pull request" for the location where the alert was last seen. This improvement makes it easier to understand the status of alerts which have been introduced into the code base. For more information, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-alert-details)." The alert list page is not changed and can be filtered by `branch`. You can use the code scanning API to retrieve more detailed branch information for alerts. For more information, see "[Code Scanning](/rest/code-scanning)" in the REST API documentation.
|
||||
# https://github.com/github/releases/issues/2050
|
||||
- |
|
||||
Code scanning now shows the details of the analysis origin of an alert. If an alert has more than one analysis origin, it is shown in the "Affected branches" sidebar and in the alert timeline. Users can hover over the analysis origin icon in the "Affected branches" sidebar to see the alert status in each analysis origin. If an alert only has a single analysis origin, no information about analysis origins is displayed on the alert page. These improvements will make it easier to understand alerts. In particular, it will help users understand those that have multiple analysis origins. This is especially useful for setups with multiple analysis configurations, such as monorepos. For more information, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-analysis-origins)."
|
||||
# https://github.com/github/releases/issues/2236
|
||||
- |
|
||||
Users can use `sort` and `direction` parameters in the REST API when retrieving secret scanning alerts, and sort based on the alert’s `created` or `updated` fields. The new parameters are available for all of your GitHub AE deployment, or for individual organizations or repositories. For more information, see the following documentation.
|
||||
|
||||
- "[List secret scanning alerts for an enterprise](/rest/secret-scanning#list-secret-scanning-alerts-for-an-enterprise)"
|
||||
- "[List secret scanning alerts for an organization](/rest/secret-scanning#list-secret-scanning-alerts-for-an-organization)"
|
||||
- "[List secret scanning alerts for a repository](/rest/secret-scanning#list-secret-scanning-alerts-for-a-repository)"
|
||||
- "[Secret Scanning](/rest/secret-scanning)" in the REST API documentation
|
||||
# https://github.com/github/releases/issues/2149
|
||||
- |
|
||||
Users can opt to receive a webhook that triggers when a secret is detected in a new location. The `secret_scanning_alert_location` webhook event includes location details, like the commit SHA, and the associated alert for the detection. A location is created for every new file path containing the detected secret. For more information, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#secret_scanning_alert_location)."
|
||||
# https://github.com/github/releases/issues/2191
|
||||
- |
|
||||
Users can optionally add a comment when dismissing a code scanning alert in the web UI or via the REST API. Dismissal comments appear in the event timeline. Users can also add or retrieve a dismissal comment via the REST API. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests#dismissing-an-alert-on-your-pull-request)" and "[Code Scanning](/rest/code-scanning#update-a-code-scanning-alert)" in the REST API documentation.
|
||||
# https://github.com/github/releases/issues/1763
|
||||
- |
|
||||
Users can now retrieve code scanning alerts for an organization using the REST API. This new API endpoint supplements the existing endpoint for repositories. For more information, see "[Code Scanning](/rest/code-scanning)" in the REST API documentation.
|
||||
# https://github.com/github/releases/issues/2263
|
||||
- |
|
||||
The contents of the `github/codeql-go` repository have moved to the `github/codeql` repository, to live alongside similar libraries for all other programming languages supported by CodeQL. The open-source CodeQL queries, libraries, and extractor for analyzing codebases written in the Go programming language with GitHub's CodeQL code analysis tools can now be found in the new location. For more information, including guidance on migrating your existing workflows, see [github/codeql-go#741](https://github.com/github/codeql-go/issues/741).
|
||||
|
||||
- heading: 'Dependabot'
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/2256
|
||||
- |
|
||||
Enterprise owners can see an overview of Dependabot alerts across the GitHub AE deployment, including a repository-centric view of application security risks, and an alert-centric view of all secret scanning and Dependabot alerts. The views are in beta and subject to change. For more information, see "[Viewing the security overview](/code-security/security-overview/viewing-the-security-overview#viewing-the-security-overview-for-an-enterprise)."
|
||||
# https://github.com/github/releases/issues/1992
|
||||
- |
|
||||
Organization owners and security managers can view Dependabot alerts in an organization's **Security** tab. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
|
||||
# https://github.com/github/releases/issues/1923
|
||||
- |
|
||||
Users can reopen a dismissed Dependabot alert using the web UI. This does not affect Dependabot pull requests or the GraphQL API. For more information, see "[About Dependabot alerts](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)."
|
||||
# https://github.com/github/releases/issues/1922
|
||||
- |
|
||||
Users can view fixed alerts from Dependabot with the GraphQL API. Users can also access and filter by state, as well as by unique numeric identifier, and filter by state on the vulnerability alert object. The following fields now exist for a `RepositoryVulnerabilityAlert`.
|
||||
|
||||
- `number`
|
||||
- `fixed_at`
|
||||
- `fix_reason`
|
||||
- `state`
|
||||
|
||||
For more information, see "[Objects](/graphql/reference/objects#repositoryvulnerabilityalert)" in the GraphQL API documentation.
|
||||
|
||||
- heading: 'Code security'
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/2096
|
||||
- |
|
||||
Organization owners and security managers can use the security overview for an organization to view a repository-centric view of application security risks, or an alert-centric view of all code scanning, Dependabot, and secret scanning alerts for all repositories in an organization. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
|
||||
# https://github.com/github/releases/issues/2098, https://github.com/github/releases/issues/2282
|
||||
- |
|
||||
GitHub Actions can enforce dependency reviews on users' pull requests by scanning for dependencies, and will warn users about associated security vulnerabilities. The `dependency-review-action` action is supported by a new API endpoint that diffs the dependencies between any two revisions. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review#dependency-review-enforcement)."
|
||||
# https://github.com/github/releases/issues/1913
|
||||
- |
|
||||
The dependency graph detects YAML files for GitHub Actions workflows. GitHub AE will display the workflow files within the **Insights** tab's dependency graph section. Repositories that publish actions will also be able to see the number of repositories that depend on that action from the "Used By" control on the repository homepage. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)."
|
||||
# https://github.com/github/releases/issues/2243
|
||||
- |
|
||||
The dependency graph detects `Cargo.toml` and `Cargo.lock` files for Rust. These files will be displayed in the **Dependency graph** section of the **Insights** tab. Users will receive Dependabot alerts and updates for vulnerabilities associated with their Rust dependencies. Package metadata, including mapping packages to repositories, will be added at a later date. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)."
|
||||
# https://github.com/github/releases/issues/1766
|
||||
- |
|
||||
If GitHub Connect is enabled for GitHub AE, users can contribute an improvement to a security advisory in the [GitHub Advisory Database](https://github.com/advisories). To contribute, click **Suggest improvements for this vulnerability** while viewing an advisory's details. For more information, see the following articles.
|
||||
|
||||
- "[Managing GitHub Connect](/admin/configuration/configuring-github-connect/managing-github-connect)"
|
||||
- "[Browsing security vulnerabilities in the GitHub Advisory Database](/enterprise-cloud@latest/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database)" in the GitHub Enterprise Cloud documentation
|
||||
- "[About GitHub Security Advisories for repositories](/enterprise-cloud@latest/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)" in the GitHub Enterprise Cloud documentation
|
||||
- "[Editing security advisories in the GitHub Advisory Database](/enterprise-cloud@latest/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)" in the GitHub Enterprise Cloud documentation
|
||||
|
||||
- heading: 'GitHub Actions'
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/2014
|
||||
- |
|
||||
People who maintain self-hosted runners now have more control over when the runners perform software updates. If you specify the `--disableupdate` flag to the runner, the runner will not try to perform an automatic software update if a newer version of the runner software is available. This allows updates to the self-hosted runner on a custom schedule, and is especially convenient if a self-hosted runner is in a container. For compatibility with the GitHub Actions service, runner software must be updated within 30 days of a new runner version being available. For more information about installation of the latest runner version, see the installation instructions for [the latest release in `actions/runner`](https://github.com/actions/runner/releases).
|
||||
# https://github.com/github/releases/issues/2102
|
||||
- |
|
||||
When using GitHub Actions, to reduce the risk of merging a change that was not reviewed by another person into a protected branch, enterprise owners and repository administrators can prevent Actions from creating pull requests. Organization owners could previously enable this restriction. For more information, see the following articles.
|
||||
|
||||
- "[Enforcing policies for GitHub Actions in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#preventing-github-actions-from-creating-or-approving-pull-requests)"
|
||||
- "[Disabling or limiting GitHub Actions for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#preventing-github-actions-from-creating-or-approving-pull-requests)"
|
||||
- "[Managing GitHub Actions settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#preventing-github-actions-from-creating-or-approving-pull-requests)"
|
||||
# https://github.com/github/releases/issues/2013
|
||||
- |
|
||||
Organization owners can increase the security of CI/CD workflows on self-hosted runners by choosing which workflows can access a runner group. Previously, any workflow in a repository, such as an issue labeler, could access the self-hosted runners available to an organization. For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-what-workflows-can-access-a-runner-group)" and the [GitHub Blog](https://github.blog/2022-03-23-github-actions-secure-self-hosted-runners-specific-workflows/).
|
||||
# https://github.com/github/releases/issues/1959
|
||||
- |
|
||||
Organization owners can control whether GitHub Actions can approve pull requests. This feature protects against a user using GitHub Actions to satisfy the "Required approvals" branch protection requirement and merging a change that was not reviewed by another user. To prevent breaking existing workflows, **Allow GitHub Actions reviews to count towards required approval** is enabled by default. Organization owners can disable the feature in the organization's GitHub Actions settings. For more information, see "[Disabling or limiting GitHub Actions for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#preventing-github-actions-from-approving-pull-requests)."
|
||||
# https://github.com/github/releases/issues/2155
|
||||
- |
|
||||
Users can write a single workflow triggered by `workflow_dispatch` and `workflow_call`, and use the `inputs` context to access input values. Previously, `workflow_dispatch` inputs were in the event payload, which increased difficulty for workflow authors who wanted to write one workflow that was both reusable and manually triggered. For workflows triggered by `workflow_dispatch`, inputs are still available in the `github.event.inputs` context to maintain compatibility. For more information, see "[Contexts](/actions/learn-github-actions/contexts#inputs-context)."
|
||||
# https://github.com/github/releases/issues/1503
|
||||
- |
|
||||
Users can now re-run only failed jobs or an individual job in a GitHub Actions workflow run. For more information, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)."
|
||||
# https://github.com/github/releases/issues/2103
|
||||
- |
|
||||
To summarize the result of a job, users can generate Markdown and publish the contents as a job summary. For example, after running tests with GitHub Actions, a summary can provide an overview of passed, failed, or skipped tests, potentially reducing the need to review the full log output. For more information, see "[Workflow commands for GitHub Actions](/actions/using-workflows/workflow-commands-for-github-actions#adding-a-job-summary)."
|
||||
# https://github.com/github/releases/issues/2161
|
||||
- |
|
||||
To more easily diagnose job execution failures during a workflow re-run, users can enable debug logging, which outputs information about a job's execution and environment. For more information, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)" and "[Using workflow run logs](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs#viewing-logs-to-diagnose-failures)."
|
||||
# https://github.com/github/releases/issues/2140
|
||||
- |
|
||||
If you manage self-hosted runners for GitHub Actions, you can ensure a consistent state on the runner itself before and after a workflow run by defining scripts to execute. By using scripts, you no longer need to require that users manually incorporate these steps into workflows. Pre- and post-job scripts are in beta and subject to change. For more information, see "[Running scripts before or after a job](/actions/hosting-your-own-runners/running-scripts-before-or-after-a-job)."
|
||||
|
||||
- heading: 'Community experience'
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/2259
|
||||
- |
|
||||
Enterprise owners can configure a policy to control whether people's usernames or full names are displayed within internal repositories. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-display-of-member-names-in-your-repositories)."
|
||||
|
||||
- heading: 'Organizations'
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/2234
|
||||
- |
|
||||
Organization owners can pin a repository to an organization's profile directly from the repository via the new **Pin repository** dropdown.
|
||||
|
||||
- heading: 'Repositories'
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/2214
|
||||
- |
|
||||
While creating a fork, users can customize the fork's name. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
|
||||
# https://github.com/github/releases/issues/2220
|
||||
- |
|
||||
Users can delete a branch that's associated with an open pull request. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
|
||||
# https://github.com/github/releases/issues/1994
|
||||
- |
|
||||
CODEOWNERS has received the following improvements.
|
||||
|
||||
- Syntax errors are now surfaced when viewing a CODEOWNERS file from the web UI. Previously, when a line in a CODEOWNERS file had a syntax error, the error would be ignored or in some cases cause the entire CODEOWNERS file to not load. GitHub Apps and Actions can access the same list of errors using new REST and GraphQL APIs. For more information, see "[Repositories](/rest/repos/repos#list-codeowners-errors)" in the REST API documentation or "[Objects](/graphql/reference/objects#repositorycodeowners)" in the GraphQL API documentation.
|
||||
- After someone creates a new pull request or pushes new changes to a draft pull request, any code owners that will be requested for review are now listed in the pull request under "Reviewers". This feature gives you an early look at who will be requested to review once the pull request is marked ready for review.
|
||||
- Comments in CODEOWNERS files can now appear at the end of a line, not just on dedicated lines.
|
||||
|
||||
For more information, see "[About code owners](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners)."
|
||||
# https://github.com/github/releases/issues/2233
|
||||
- |
|
||||
When a user renames or moves a file to a new directory, if at least half of the file's contents are identical, the commit history indicates that the file was renamed, similar to `git log --follow`. For more information, see the [GitHub Blog](https://github.blog/changelog/2022-06-06-view-commit-history-across-file-renames-and-moves/).
|
||||
# https://github.com/github/releases/issues/2093
|
||||
- |
|
||||
Users can require a successful deployment of a branch before anyone can merge the pull request associated with the branch. For more information, see "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#require-deployments-to-succeed-before-merging)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule)."
|
||||
# https://github.com/github/releases/issues/1793
|
||||
- |
|
||||
Repository administrators can now configure tag protection rules to protect a repository's tags. Once protected by a tag protection rule, tags matching a specified name pattern can only be created and deleted by users with maintain or admin access to the repository. For more information, see "[Configuring tag protection rules](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)."
|
||||
# https://github.com/github/releases/issues/2090
|
||||
- |
|
||||
Users can ignore revisions in the blame view by creating a `.git-blame-ignore-revs` file in the root of a repository. For more information, see "[Viewing a file](/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view)."
|
||||
# https://github.com/github/releases/issues/2173
|
||||
- |
|
||||
Users can grant exceptions to GitHub Apps for any branch protection rule that supports exceptions. For more information, see "[About apps](/developers/apps/getting-started-with-apps/about-apps)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule)."
|
||||
|
||||
- heading: 'Commits'
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/2306
|
||||
- |
|
||||
For public GPG signing keys that are expired or revoked, GitHub AE verifies Git commit signatures and show commits as verified if the user made the commit while the key was still valid. Users can also upload expired or revoked GPG keys. For more information, see "[About commit signature verification](/authentication/managing-commit-signature-verification/about-commit-signature-verification)."
|
||||
# https://github.com/github/releases/issues/1977
|
||||
- |
|
||||
To affirm that a commit complies with the rules and licensing governing a repository, organization owners and repository administrators can now require developers to sign off on commits made through the web interface. For more information, see "[Managing the commit signoff policy for your organization](/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization)" and "[Managing the commit signoff policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)."
|
||||
|
||||
- heading: 'Pull requests'
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/2261
|
||||
- |
|
||||
Using the file tree located in the **Files changed** tab of a pull request, users can navigate modified files, understand the size and scope of changes, and focus reviews. The file tree appears if a pull request modifies at least two files, and the browser window is sufficiently wide. For more information, see "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)" and "[Filtering files in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)."
|
||||
# https://github.com/github/releases/issues/2167
|
||||
- |
|
||||
Users can default to using pull requests titles as the commit message for all squash merges. For more information, see "[Configuring commit squashing for pull requests](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)."
|
||||
# https://github.com/github/releases/issues/1566
|
||||
- |
|
||||
The **Update branch** button on the pull request page lets users update a pull request's branch with the latest changes from the base branch. This is useful for verifying that the pull request's changes are compatible with the current version of the base branch before you merge. Two enhancements provide more ways to keep a branch up to date.
|
||||
|
||||
- When a pull request's topic branch is out of date with the base branch, users can update the branch by rebasing on the latest version of the base branch. Rebasing applies the changes from the topic branch onto the latest version of the base branch, resulting in a branch with a linear history since no merge commit is created. To update by rebasing, click the drop-down menu next to the **Update Branch** button, click **Update with rebase**, and then click **Rebase branch**. Previously, **Update branch** performed a traditional merge that always resulted in a merge commit in your pull request branch. This option is still available, but now users have the choice. For more information, see "[Keeping your pull request in sync with the base branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)."
|
||||
- A new repository setting allows the **Update branch** button to always be available when a pull request's topic branch is not up to date with the base branch. Previously, this button was only available when the **Require branches to be up to date before merging** branch protection setting was enabled. People with admin or maintainer access can manage the **Always suggest updating pull request branches** setting from the **Pull Requests** section in repository settings. For more information, see "[Managing suggestions to update pull request branches](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches)."
|
||||
|
||||
- heading: 'Releases'
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/2281
|
||||
- |
|
||||
When viewing the details for a particular release, users can see the creation date for each release asset. For more information, see "[Viewing your repository's releases and tags](/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags)."
|
||||
# https://github.com/github/releases/issues/2279
|
||||
- |
|
||||
While creating a release with automatically generated release notes, users can see the tag identified as the previous release, then choose to select a different tag to specify as the previous release. For more information, see "[Automatically generated release notes](/repositories/releasing-projects-on-github/automatically-generated-release-notes)."
|
||||
# https://github.com/github/releases/issues/2028
|
||||
- heading: 'Gist'
|
||||
notes:
|
||||
- |
|
||||
Gists now only show the 30 most recent comments when first displayed. Users can click **Load earlier comments...** to view more. This allows gists that have many comments to appear more quickly. For more information, see "[Editing and sharing content with gists](/get-started/writing-on-github/editing-and-sharing-content-with-gists)."
|
||||
|
||||
- heading: 'Markdown'
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/2260
|
||||
- |
|
||||
Editing Markdown in the web interface has been improved.
|
||||
|
||||
- After a user selects text and pastes a URL, the selected text will become a Markdown link to the pasted URL.
|
||||
- When a user pastes spreadsheet cells or HTML tables, the resulting text will render as a table.
|
||||
- When a user copies text containing links, the pasted text will include the link as a Markdown link.
|
||||
|
||||
For more information, see "[Basic writing and formatting syntax](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#links)."
|
||||
# https://github.com/github/releases/issues/2258
|
||||
- |
|
||||
When editing a Markdown file in the web interface, clicking the **Preview** tab will automatically scroll to the place in the preview that you were editing. The scroll location is based on the position of the cursor before clicking the **Preview** tab.
|
||||
|
||||
- heading: 'Accessibility'
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/2011
|
||||
- |
|
||||
A light high-contrast theme, with greater contrast between foreground and background elements, is now available. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)."
|
||||
|
||||
changes:
|
||||
# https://github.com/github/releases/issues/2071
|
||||
- |
|
||||
Lists of repositories owned by a user or organization now have an additional filter option, "Templates", making it easier to find template repositories.
|
||||
# https://github.com/github/releases/issues/1947
|
||||
- |
|
||||
GitHub AE can display several common image formats, including PNG, JPG, GIF, PSD, and SVG, and provides several ways to compare differences between versions. When reviewing added or changed images in a pull request, previews of those images are now shown by default. Previously, users would see a message indicating that binary files could not be shown, and would need to toggle the "Display rich diff" option. For more information, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files)."
|
||||
# https://github.com/github/releases/issues/2036
|
||||
- |
|
||||
Settings pages for users, organizations, repositories, and teams have been redesigned, grouping similar settings pages into sections for improved information architecture and discoverability. For more information, see the [GitHub Changelog](https://github.blog/changelog/2022-02-02-redesign-of-githubs-settings-pages/).
|
||||
- |
|
||||
Interactive elements in the web interface such as links and buttons show a visible outline when focused with a keyboard, to help users find the current position on a page. In addition, when focused, form fields have a higher contrast outline.
|
||||
# https://github.com/github/releases/issues/2129
|
||||
- |
|
||||
Focusing or hovering over a label now displays a tooltip with the label's description.
|
||||
- |
|
||||
If a user refreshes the page while creating a new issue or pull request, the assignees, reviewers, labels, and projects will all be preserved.
|
||||
# https://github.com/github/releases/issues/2063
|
||||
- |
|
||||
To use the device authorization flow for OAuth and GitHub Apps, app authors must manually enable the feature. This change reduces the likelihood of apps being used in phishing attacks against GitHub AE users by ensuring integrators are aware of the risks and make a conscious choice to support this form of authentication. Users who own or manage an OAuth App or GitHub App and want to use the device flow can enable it for an app via the app's settings page. The device flow API endpoints will respond with status code `400` to apps that have not enabled this feature. For more information, see "[Authorizing OAuth Apps](/developers/apps/building-oauth-apps/authorizing-oauth-apps#device-flow)."
|
||||
|
||||
deprecations:
|
||||
- |
|
||||
The theme picker for GitHub Pages has been removed from the Pages settings. For more information about configuration of themes for GitHub Pages, see "[Adding a theme to your GitHub Pages site using Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll)."
|
||||
@@ -1,35 +0,0 @@
|
||||
# Release notes for GitHub AE
|
||||
|
||||
Rendered here: https://docs.github.com/en/github-ae@latest/admin/release-notes <!-- markdownlint-disable-line search-replace -->
|
||||
|
||||
## How it works
|
||||
|
||||
### Placeholder content file
|
||||
|
||||
A content file exists in `content/admin/release-notes.md`. It has a special frontmatter property `layout: release-notes` and no Markdown content. The source of the release notes comes from YAML data.
|
||||
|
||||
### YAML source
|
||||
|
||||
The source data for the release notes lives in this directory (`data/release-notes/github-ae`).
|
||||
|
||||
The directories are named by internal GHAE release (with a hyphen instead of a period). The "current" release (i.e., the one that evaluates to `@latest`) is set via the `internalLatestRelease` property on the GHAE entry in `lib/all-versions.js`.
|
||||
|
||||
GHAE releases do not have patches, but due to precedent in the Enterprise Server release notes (which do have patches), the YAML files are named `0.yml`.
|
||||
|
||||
Note that patch files can be deprecated individually (i.e., hidden on the docs site) by an optional `deprecated: true` property.
|
||||
|
||||
### Middleware processing
|
||||
|
||||
The YAML data is processed and sorted by `src/release-notes/middleware/ghae-release-notes.js` and added to the `context` object.
|
||||
|
||||
### Layouts
|
||||
|
||||
The `context` object data is rendered by `components/release-notes`.
|
||||
|
||||
The release notes page has a custom design with CSS in `stylesheets/release-notes.scss`.
|
||||
|
||||
### Schema
|
||||
|
||||
The schema that validates the YAML data lives in `src/content-linter/lib/release-notes-schema.js`. See the schema file to find out the required and optional properties.
|
||||
|
||||
The schema is exercised by a test in `src/content-linter/tests/lint-files.js`. The test will fail if the data does not pass validation.
|
||||
@@ -6,7 +6,7 @@
|
||||
| 122 | SSH | Instance shell access. _The default SSH port (22) is dedicated to application git+ssh network traffic._ |
|
||||
| 161/UDP | SNMP | Required for network monitoring protocol operation. |
|
||||
| 443 | HTTPS | Web application and Git over HTTPS access. |
|
||||
| 1194/UDP | VPN | Secure replication network tunnel in high availability configuration. |
|
||||
| 1194/UDP | VPN | Secure replication network tunnel in high availability configuration. _Encrypted using WireGuard._ |
|
||||
| 8080 | HTTP | Plain-text web based {% data variables.enterprise.management_console %}. _Not required unless SSL is disabled manually._ |
|
||||
| 8443 | HTTPS | Secure web based {% data variables.enterprise.management_console %}. _Required for basic installation and configuration._ |
|
||||
| 9418 | Git | Simple Git protocol port. Clone and fetch operations to public repositories only. _Unencrypted network communication._ {% data reusables.enterprise_installation.when-9418-necessary %} |
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
contact_ent_support: '[GitHub Enterprise Support](https://support.github.com)'
|
||||
|
||||
# GitHub Support (with versioning for GHES, GHAE) - when users need to open a ticket through the support portal
|
||||
# GitHub Support (with versioning for GHES) - when users need to open a ticket through the support portal
|
||||
contact_support: >-
|
||||
{% ifversion fpt or ghec %}us through the [GitHub Support portal](https://support.github.com){% elsif ghes %}your site administrator{% endif %}
|
||||
|
||||
|
||||
@@ -16,4 +16,3 @@ prodname_unified_search: 'unified search'
|
||||
|
||||
# Entra ID (previously known as Azure AD)
|
||||
ghes_azure_ad_app_link: '[GitHub Enterprise Server application](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/aad.githubenterpriseserver)'
|
||||
ae_azure_ad_app_link: '[GitHub AE application](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/aad.ghae)'
|
||||
|
||||
Reference in New Issue
Block a user