Fix outdated-release-phase-terminology warnings (#58306)
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
This commit is contained in:
Joe Clark
@@ -41,7 +41,7 @@ The following IdPs are partner IdPs. They offer an application that you can use
|
||||
|
||||
* Microsoft Entra ID
|
||||
* Okta
|
||||
* PingFederate (beta)
|
||||
* PingFederate ({% data variables.release-phases.public_preview %})
|
||||
|
||||
When you use a single partner IdP for both authentication and provisioning, {% data variables.product.company_short %} provides support for the application on the partner IdP and the IdP's integration with {% data variables.product.prodname_dotcom %}. Support for PingFederate is in {% data variables.release-phases.public_preview %}.
|
||||
|
||||
|
||||
@@ -352,7 +352,7 @@ The following properties are supported in `qlpack.yml` files.
|
||||
|
||||
#### `libraryPathDependencies`
|
||||
|
||||
* Optional, deprecated. Use the `dependencies` property instead.
|
||||
* Optional, {% data variables.release-phases.closing_down %}. Use the `dependencies` property instead.
|
||||
* Previously used to define the names of any {% data variables.product.prodname_codeql %} packs that this {% data variables.product.prodname_codeql %} pack depends on, as an array. This gives the pack access to any libraries, database schema, and query suites defined in the dependency. For example:
|
||||
|
||||
```yaml
|
||||
|
||||
@@ -44,7 +44,7 @@ The rest of this article covers the practical aspects of modelling dependencies
|
||||
|
||||
1. In the "Databases" view, select the {% data variables.product.prodname_codeql %} database that you want to model from.
|
||||
|
||||
1. In the {% data variables.product.prodname_codeql %} "Method Modeling" view, click **Start modeling** to display the model editor. Alternatively, use the {% data variables.product.prodname_vscode_command_palette_shortname %} to run the **{% data variables.product.prodname_codeql %}: Open Model Editor (Beta)** command.
|
||||
1. In the {% data variables.product.prodname_codeql %} "Method Modeling" view, click **Start modeling** to display the model editor. Alternatively, use the {% data variables.product.prodname_vscode_command_palette_shortname %} to run the **{% data variables.product.prodname_codeql %}: Open Model Editor (Beta)** command. <!-- markdownlint-disable-line outdated-release-phase-terminology --> <!-- "Beta" is in the name of the command in the VS Code extension -->
|
||||
|
||||
1. The {% data variables.product.prodname_codeql %} model editor runs a series of telemetry queries to identify APIs in the code, and the editor is displayed in a new tab.
|
||||
|
||||
|
||||
@@ -828,6 +828,8 @@ New version `2.0.0`
|
||||
|
||||
### Versioning tags
|
||||
|
||||
<!-- markdownlint-disable outdated-release-phase-terminology -->
|
||||
|
||||
* Represent stages in the software release lifecycle, such as alpha, beta, and stable versions.
|
||||
* Allow publishers to distribute their packages more effectively.
|
||||
* Indicate the stability of a version and communicate what users should expect in terms of features and stability.
|
||||
@@ -849,6 +851,8 @@ New version `2.0.0`
|
||||
* **`release`:** The official release version.
|
||||
* **`stable`:** The most reliable, production-ready version.
|
||||
|
||||
<!-- markdownlint-enable outdated-release-phase-terminology -->
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Top-level `registries` key
|
||||
|
||||
@@ -22,6 +22,6 @@ category:
|
||||
- Author and optimize with Copilot
|
||||
---
|
||||
|
||||
# Replacing the deprecated {% data variables.product.prodname_copilot_short %} extension
|
||||
# Replacing the {% data variables.release-phases.retired %} {% data variables.product.prodname_copilot_short %} extension
|
||||
|
||||
The {% data variables.product.prodname_copilot %} extension for {% data variables.product.prodname_cli %} has been deprecated. It has been replaced by the new {% data variables.copilot.copilot_cli %}. See [AUTOTITLE](/copilot/concepts/agents/about-copilot-cli).
|
||||
The {% data variables.product.prodname_copilot %} extension for {% data variables.product.prodname_cli %} is {% data variables.release-phases.retired %}. It has been replaced by the new {% data variables.copilot.copilot_cli %}. See [AUTOTITLE](/copilot/concepts/agents/about-copilot-cli).
|
||||
|
||||
@@ -93,7 +93,7 @@ First, you need to configure the MCP servers that you anticipate {% data variabl
|
||||
|
||||
* **{% data variables.product.github %} MCP server**: Configure the {% data variables.product.github %} MCP server to enable {% data variables.product.prodname_copilot_short %} to access your repository, examine your codebase, research existing issues, create branches, and manage pull requests. See [AUTOTITLE](/copilot/customizing-copilot/using-model-context-protocol/using-the-github-mcp-server).
|
||||
|
||||
* **Figma MCP server**: Configure the Figma MCP server to allow {% data variables.product.prodname_copilot_short %} to access design files that include accessibility specifications, such as color contrast requirements, focus states, and interaction patterns. See [Figma-Context-MCP](https://github.com/GLips/Figma-Context-MCP) or try out the [Dev Mode MCP server](https://help.figma.com/hc/en-us/articles/32132100833559-Guide-to-the-Dev-Mode-MCP-Server) in open beta.
|
||||
* **Figma MCP server**: Configure the Figma MCP server to allow {% data variables.product.prodname_copilot_short %} to access design files that include accessibility specifications, such as color contrast requirements, focus states, and interaction patterns. See [Figma-Context-MCP](https://github.com/GLips/Figma-Context-MCP) or try out the [Dev Mode MCP server](https://help.figma.com/hc/en-us/articles/32132100833559-Guide-to-the-Dev-Mode-MCP-Server).
|
||||
|
||||
* **Playwright MCP server**: Set up the Playwright MCP server to enable {% data variables.product.prodname_copilot_short %} to write and run automated accessibility tests, including screen reader compatibility and keyboard navigation tests. See [mcp-playwright](https://github.com/executeautomation/mcp-playwright).
|
||||
|
||||
|
||||
@@ -28,7 +28,7 @@ Standard {% data variables.contact.github_support %} is provided as part of your
|
||||
|
||||
* Escalation management: Dedicated escalation management ensures that complex issues are addressed promptly and efficiently, with a clear path for escalating critical incidents.
|
||||
|
||||
* Early access to new features: Participation in beta programs and early access to new features allows you to stay ahead of the curve with the latest {% data variables.product.github %} innovations.
|
||||
* Early access to new features: Participation in {% data variables.release-phases.preview %} programs and early access to new features allows you to stay ahead of the curve with the latest {% data variables.product.github %} innovations.
|
||||
|
||||
There are two support plans available with {% data variables.contact.premium_support %}:
|
||||
|
||||
|
||||
@@ -59,7 +59,7 @@ Branch filters allow you to filter commit notifications based on branch names. B
|
||||
|`/github subscribe owner/repo commits:feature/*`|Receive commit notifications for all branches that start with `feature/`.|
|
||||
|`/github subscribe owner/repo commits:*`|Receive commit notifications for all branches.|
|
||||
|
||||
>[!NOTE] You may have previously used the `commits:all` filter to receive commit notifications for all branches. This filter is now deprecated. To receive commit notifications for all branches, use the `commits:*` filter instead. If you have previously set up the `commits:all` filter, it will continue to work until you update your configuration to use the `commits:*` filter.
|
||||
>[!NOTE] You may have previously used the `commits:all` filter to receive commit notifications for all branches. This filter is {% data variables.release-phases.closing_down %}. To receive commit notifications for all branches, use the `commits:*` filter instead. If you have previously set up the `commits:all` filter, it will continue to work until you update your configuration to use the `commits:*` filter.
|
||||
|
||||
### Label filters for issue and pull request notifications
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ type: how_to
|
||||
* To create a new milestone, click **New Milestone**.
|
||||
* To edit a milestone, next to the milestone you want to edit, click **Edit**.
|
||||
|
||||
|
||||
 <!-- markdownlint-disable-line outdated-release-phase-terminology -->
|
||||
1. Type the milestone's title, description, or other changes, and click **Create milestone** or **Save changes**. Milestones will render Markdown syntax. For more information about Markdown syntax, see [AUTOTITLE](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax).
|
||||
|
||||
## Deleting milestones
|
||||
@@ -36,4 +36,4 @@ When you delete milestones, issues and pull requests are not affected.
|
||||
{% data reusables.project-management.milestones %}
|
||||
1. Next to the milestone you want to delete, click **Delete**.
|
||||
|
||||
|
||||
 <!-- markdownlint-disable-line outdated-release-phase-terminology -->
|
||||
|
||||
@@ -64,10 +64,14 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da
|
||||
|
||||
1. Follow the interactive prompts. Alternatively, you can specify arguments to skip these prompts. For more information about possible arguments, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_release_create). For example, this command creates a prerelease with the specified title and notes.
|
||||
|
||||
<!-- markdownlint-disable outdated-release-phase-terminology --> <!-- disable the outdated-release-phase-terminology rule since "beta" is part of the CLI command -->
|
||||
|
||||
```shell
|
||||
gh release create v1.3.2 --title "v1.3.2 (beta)" --notes "this is a {% data variables.release-phases.public_preview %} release" --prerelease
|
||||
```
|
||||
|
||||
<!-- markdownlint-enable outdated-release-phase-terminology -->
|
||||
|
||||
If you @mention any {% data variables.product.github %} users in the notes, the published release will include a **Contributors** section with an avatar list of all the mentioned users.
|
||||
|
||||
{% endcli %}
|
||||
|
||||
@@ -250,7 +250,7 @@ sections:
|
||||
In GitHub Enterprise Server 3.17, GitHub will migrate tag protection rules to a ruleset and the tag protection rule feature will no longer be available. Prior to upgrading to 3.17, you can use the [migration feature](https://github.blog/changelog/2023-10-18-migrate-tag-protections-to-repository-rules/) to move your tag protection rules.
|
||||
# https://github.com/github/releases/issues/5381
|
||||
- |
|
||||
In GitHub Enterprise Server 3.17, GitHub will deprecate the Docker registry for GitHub Packages in favor of the GitHub Container Registry, which supports Docker packages. All packages in the Docker registry will be deleted and cannot be fetched past the deprecation date.
|
||||
In GitHub Enterprise Server 3.17, GitHub will be closing down the Docker registry for GitHub Packages in favor of the GitHub Container Registry, which supports Docker packages. All packages in the Docker registry will be deleted and cannot be fetched past the closing down date.
|
||||
# https://github.com/github/releases/issues/5292
|
||||
- |
|
||||
In GitHub Enterprise Server 3.17, Dependabot will no longer support Python 3.8, which has reached its end-of-life. If you continue to use Python 3.8, Dependabot will not be able to create pull requests to update dependencies. If this affects you, we recommend updating to a supported release of Python. As of February 2025, Python 3.13 is the newest supported release.
|
||||
@@ -259,11 +259,11 @@ sections:
|
||||
In GitHub Enterprise Server 3.17, Dependabot will no longer support NPM version 6, which has reached its end-of-life. If you continue to use NPM version 6, Dependabot will be unable to create pull requests to update dependencies. If this affects you, we recommend updating to a supported release of NPM. As of December 2024, NPM 9 is the newest supported release.
|
||||
# https://github.com/github/releases/issues/4710
|
||||
- |
|
||||
In GitHub Enterprise Server 3.17 and later, the field `cvss` for GitHub security advisories in the REST & GraphQL APIs will be deprecated in favour of the new `cvss_severities` field.
|
||||
In GitHub Enterprise Server 3.17 and later, the field `cvss` for GitHub security advisories in the REST & GraphQL APIs will be closing down in favour of the new `cvss_severities` field.
|
||||
|
||||
retired:
|
||||
- |
|
||||
Team discussions have been removed from GitHub Enterprise Server. The sunset of this feature was announced in 2023. See the [GitHub Blog post](https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/).
|
||||
Team discussions have been removed from GitHub Enterprise Server. This feature was retired in 2023. See the [GitHub Blog post](https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/).
|
||||
# https://github.com/github/releases/issues/4964
|
||||
- |
|
||||
In GitHub Enterprise Server 3.16, the `/explore` functionality, including the Activity and Trending pages, is removed.
|
||||
@@ -272,4 +272,4 @@ sections:
|
||||
GitHub no longer supports .NET 6 in GitHub Enterprise Server 3.16 and later.
|
||||
# https://github.com/github/releases/issues/4535
|
||||
- |
|
||||
As of October 15th, 2024, you will no longer be able to enable or disable GitHub security features for repositories from the organization-level security coverage view. This feature has been deprecated and replaced with code security configurations for managing these settings. See the [GitHub blog post](https://github.blog/changelog/2024-10-17-new-code-security-configurations-let-you-set-security-features-at-the-organization-level/).
|
||||
As of October 15th, 2024, you will no longer be able to enable or disable GitHub security features for repositories from the organization-level security coverage view. This feature has been retired and replaced with code security configurations for managing these settings. See the [GitHub blog post](https://github.blog/changelog/2024-10-17-new-code-security-configurations-let-you-set-security-features-at-the-organization-level/).
|
||||
|
||||
@@ -238,7 +238,7 @@ sections:
|
||||
In GitHub Enterprise Server 3.17, GitHub will migrate tag protection rules to a ruleset and the tag protection rule feature will no longer be available. Prior to upgrading to 3.17, you can use the [migration feature](https://github.blog/changelog/2023-10-18-migrate-tag-protections-to-repository-rules/) to move your tag protection rules.
|
||||
# https://github.com/github/releases/issues/5381
|
||||
- |
|
||||
In GitHub Enterprise Server 3.17, GitHub will deprecate the Docker registry for GitHub Packages in favor of the GitHub Container Registry, which supports Docker packages. All packages in the Docker registry will be deleted and cannot be fetched past the deprecation date.
|
||||
In GitHub Enterprise Server 3.17, GitHub will be closing down the Docker registry for GitHub Packages in favor of the GitHub Container Registry, which supports Docker packages. All packages in the Docker registry will be deleted and cannot be fetched past the closing down date.
|
||||
# https://github.com/github/releases/issues/5292
|
||||
- |
|
||||
In GitHub Enterprise Server 3.17, Dependabot will no longer support Python 3.8, which has reached its end-of-life. If you continue to use Python 3.8, Dependabot will not be able to create pull requests to update dependencies. If this affects you, we recommend updating to a supported release of Python. As of February 2025, Python 3.13 is the newest supported release.
|
||||
@@ -247,14 +247,14 @@ sections:
|
||||
In GitHub Enterprise Server 3.17, Dependabot will no longer support NPM version 6, which has reached its end-of-life. If you continue to use NPM version 6, Dependabot will be unable to create pull requests to update dependencies. If this affects you, we recommend updating to a supported release of NPM. As of December 2024, NPM 9 is the newest supported release.
|
||||
# https://github.com/github/releases/issues/4710
|
||||
- |
|
||||
In GitHub Enterprise Server 3.17 and later, the field `cvss` for GitHub security advisories in the REST & GraphQL APIs will be deprecated in favour of the new `cvss_severities` field.
|
||||
In GitHub Enterprise Server 3.17 and later, the field `cvss` for GitHub security advisories in the REST & GraphQL APIs will be closing down in favour of the new `cvss_severities` field.
|
||||
# https://github.com/github/releases/issues/4964
|
||||
- |
|
||||
In GitHub Enterprise Server 3.17 and later, the Trending functionality under /explore will be removed. It was supposed be removed in version 3.16.
|
||||
|
||||
retired:
|
||||
- |
|
||||
Team discussions have been removed from GitHub Enterprise Server. The sunset of this feature was announced in 2023. See the [GitHub Blog post](https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/).
|
||||
Team discussions have been removed from GitHub Enterprise Server. This feature was retired in 2023. See the [GitHub Blog post](https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/).
|
||||
# https://github.com/github/releases/issues/4964
|
||||
- |
|
||||
In GitHub Enterprise Server 3.16, the Activity functionality under /explore is removed.
|
||||
@@ -263,7 +263,7 @@ sections:
|
||||
GitHub no longer supports .NET 6 in GitHub Enterprise Server 3.16 and later.
|
||||
# https://github.com/github/releases/issues/4535
|
||||
- |
|
||||
As of October 15th, 2024, you will no longer be able to enable or disable GitHub security features for repositories from the organization-level security coverage view. This feature has been deprecated and replaced with code security configurations for managing these settings. See the [GitHub blog post](https://github.blog/changelog/2024-10-17-new-code-security-configurations-let-you-set-security-features-at-the-organization-level/).
|
||||
As of October 15th, 2024, you will no longer be able to enable or disable GitHub security features for repositories from the organization-level security coverage view. This feature has been retired and replaced with code security configurations for managing these settings. See the [GitHub blog post](https://github.blog/changelog/2024-10-17-new-code-security-configurations-let-you-set-security-features-at-the-organization-level/).
|
||||
|
||||
errata:
|
||||
- |
|
||||
|
||||
@@ -15,7 +15,7 @@ sections:
|
||||
- |
|
||||
Applying a new GitHub Enterprise Server license using the Management Console would sometimes fail with a HTTP 500 error.
|
||||
- |
|
||||
Users saw outdated references to delegated bypass for push protection being in beta in the documentation for webhooks. Users may also have noticed unexpected behavior related to filtering newly approved push protection bypass requests on repository and organization request list pages.
|
||||
Users saw outdated references to delegated bypass for push protection being in public preview in the documentation for webhooks. Users may also have noticed unexpected behavior related to filtering newly approved push protection bypass requests on repository and organization request list pages.
|
||||
changes:
|
||||
- |
|
||||
Site administrators can now set `innodb_buffer_pool_size` in megabytes for MySQL using `ghe-config mysql.innodb-buffer-pool-size VALUE`.
|
||||
|
||||
@@ -247,7 +247,7 @@ sections:
|
||||
The /explore functionality, including the Activity and Trending pages, is no longer available. Users can no longer access these pages to discover trending repositories or recent activity.
|
||||
# https://github.com/github/releases/issues/6045
|
||||
- |
|
||||
The ability to bulk convert issues to discussions using labels is deprecated. Users can continue to convert individual issues to discussions manually using the "Convert to discussion" option. See [AUTOTITLE](/discussions/managing-discussions-for-your-community/moderating-discussions).
|
||||
The ability to bulk convert issues to discussions using labels is closing down. Users can continue to convert individual issues to discussions manually using the "Convert to discussion" option. See [AUTOTITLE](/discussions/managing-discussions-for-your-community/moderating-discussions).
|
||||
# https://github.com/github/releases/issues/4977
|
||||
- |
|
||||
GitHub Actions users should update workflows that modify check run statuses via the REST API. GitHub will restrict the ability to change check run status for runs created by Actions to prevent inconsistent state changes. Review your workflows to ensure compatibility with this update.
|
||||
@@ -259,4 +259,4 @@ sections:
|
||||
The announcement banner GraphQL fields have been replaced. Users can now manage instance-wide announcements through updated GraphQL fields, improving consistency and control for administrators. The existing individual fields following the `announcementX` pattern have been removed, and the new fields are within the `announcementBanner` object.
|
||||
# https://github.com/github/releases/issues/5811
|
||||
- |
|
||||
Automatic watching of repositories and teams has been deprecated. Users will no longer be auto-subscribed when joining organizations or teams, reducing notification noise and confusion. Existing auto-watching subscriptions remain unchanged; users stay subscribed to previously watched repositories or teams. See [AUTOTITLE](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#automatic-watching).
|
||||
Automatic watching of repositories and teams has been retired. Users will no longer be auto-subscribed when joining organizations or teams, reducing notification noise and confusion. Existing auto-watching subscriptions remain unchanged; users stay subscribed to previously watched repositories or teams. See [AUTOTITLE](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#automatic-watching).
|
||||
@@ -236,7 +236,7 @@ sections:
|
||||
The /explore functionality, including the Activity and Trending pages, is no longer available. Users can no longer access these pages to discover trending repositories or recent activity.
|
||||
# https://github.com/github/releases/issues/6045
|
||||
- |
|
||||
The ability to bulk convert issues to discussions using labels is deprecated. Users can continue to convert individual issues to discussions manually using the "Convert to discussion" option. See [AUTOTITLE](/discussions/managing-discussions-for-your-community/moderating-discussions).
|
||||
The ability to bulk convert issues to discussions using labels is closing down. Users can continue to convert individual issues to discussions manually using the "Convert to discussion" option. See [AUTOTITLE](/discussions/managing-discussions-for-your-community/moderating-discussions).
|
||||
# https://github.com/github/releases/issues/4977
|
||||
- |
|
||||
GitHub Actions users should update workflows that modify check run statuses via the REST API. GitHub will restrict the ability to change check run status for runs created by Actions to prevent inconsistent state changes. Review your workflows to ensure compatibility with this update.
|
||||
@@ -248,4 +248,4 @@ sections:
|
||||
The announcement banner GraphQL fields have been replaced. Users can now manage instance-wide announcements through updated GraphQL fields, improving consistency and control for administrators. The existing individual fields following the `announcementX` pattern have been removed, and the new fields are within the `announcementBanner` object.
|
||||
# https://github.com/github/releases/issues/5811
|
||||
- |
|
||||
Automatic watching of repositories and teams has been deprecated. Users will no longer be auto-subscribed when joining organizations or teams, reducing notification noise and confusion. Existing auto-watching subscriptions remain unchanged; users stay subscribed to previously watched repositories or teams. See [AUTOTITLE](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#automatic-watching).
|
||||
Automatic watching of repositories and teams is closing down. Users will no longer be auto-subscribed when joining organizations or teams, reducing notification noise and confusion. Existing auto-watching subscriptions remain unchanged; users stay subscribed to previously watched repositories or teams. See [AUTOTITLE](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#automatic-watching).
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
When a pattern matches the `branches-ignore` or `tags-ignore` pattern, the workflow will not run. The patterns defined in `branches` and `tags` are evaluated against the Git ref's name. For example, the following workflow would run whenever there is a `push` event, unless the `push` event is to:
|
||||
|
||||
* A branch named `mona/octocat` (`refs/heads/mona/octocat`)
|
||||
* A branch whose name matches `releases/**-alpha`, like `releases/beta/3-alpha` (`refs/heads/releases/beta/3-alpha`)
|
||||
* A branch whose name matches `releases/**-alpha`, like `releases/beta/3-alpha` (`refs/heads/releases/beta/3-alpha`) <!-- markdownlint-disable-line outdated-release-phase-terminology -->
|
||||
* A tag named `v2` (`refs/tags/v2`)
|
||||
* A tag whose name starts with `v1.`, like `v1.9` (`refs/tags/v1.9`)
|
||||
|
||||
|
||||
@@ -7,7 +7,7 @@ The order that you define patterns matters.
|
||||
* A matching negative pattern (prefixed with `!`) after a positive match will exclude the Git ref.
|
||||
* A matching positive pattern after a negative match will include the Git ref again.
|
||||
|
||||
The following workflow will run on pushes to `releases/10` or `releases/beta/mona`, but not on `releases/10-alpha` or `releases/beta/3-alpha` because the negative pattern `!releases/**-alpha` follows the positive pattern.
|
||||
The following workflow will run on pushes to `releases/10` or `releases/beta/mona`, but not on `releases/10-alpha` or `releases/beta/3-alpha` because the negative pattern `!releases/**-alpha` follows the positive pattern. <!-- markdownlint-disable-line outdated-release-phase-terminology -->
|
||||
|
||||
```yaml
|
||||
on:
|
||||
|
||||
@@ -32,7 +32,7 @@ The order that you define patterns matters.
|
||||
* A matching negative pattern (prefixed with `!`) after a positive match will exclude the branch.
|
||||
* A matching positive pattern after a negative match will include the branch again.
|
||||
|
||||
For example, a workflow with the following trigger will run when the workflow named `Build` runs on a branch that is named `releases/10` or `releases/beta/mona` but will not `releases/10-alpha`, `releases/beta/3-alpha`, or `main`.
|
||||
For example, a workflow with the following trigger will run when the workflow named `Build` runs on a branch that is named `releases/10` or `releases/beta/mona` but will not `releases/10-alpha`, `releases/beta/3-alpha`, or `main`. <!-- markdownlint-disable-line outdated-release-phase-terminology -->
|
||||
|
||||
```yaml
|
||||
on:
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
When a pattern matches the `branches-ignore` pattern, the workflow will not run. The patterns defined in `branches-ignore` are evaluated against the Git ref's name. For example, the following workflow would run whenever there is a `pull_request` event unless the pull request is targeting:
|
||||
|
||||
* A branch named `mona/octocat` (`refs/heads/mona/octocat`)
|
||||
* A branch whose name matches `releases/**-alpha`, like `releases/beta/3-alpha` (`refs/heads/releases/beta/3-alpha`)
|
||||
* A branch whose name matches `releases/**-alpha`, like `releases/beta/3-alpha` (`refs/heads/releases/beta/3-alpha`) <!-- markdownlint-disable-line outdated-release-phase-terminology -->
|
||||
|
||||
```yaml
|
||||
on:
|
||||
|
||||
@@ -7,7 +7,7 @@ The order that you define patterns matters.
|
||||
* A matching negative pattern (prefixed with `!`) after a positive match will exclude the Git ref.
|
||||
* A matching positive pattern after a negative match will include the Git ref again.
|
||||
|
||||
The following workflow will run on `pull_request` events for pull requests that target `releases/10` or `releases/beta/mona`, but not for pull requests that target `releases/10-alpha` or `releases/beta/3-alpha` because the negative pattern `!releases/**-alpha` follows the positive pattern.
|
||||
The following workflow will run on `pull_request` events for pull requests that target `releases/10` or `releases/beta/mona`, but not for pull requests that target `releases/10-alpha` or `releases/beta/3-alpha` because the negative pattern `!releases/**-alpha` follows the positive pattern. <!-- markdownlint-disable-line outdated-release-phase-terminology -->
|
||||
|
||||
```yaml
|
||||
on:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
{% ifversion management-console-manage-ghes-parity %}
|
||||
|
||||
> [!NOTE]
|
||||
> The {% data variables.enterprise.management_console %} endpoints will be deprecated in a future version of {% data variables.product.prodname_ghe_server %}. You can access the same functionality using the Manage {% data variables.product.prodname_ghe_server %} endpoints. For more information, see [AUTOTITLE](/rest/enterprise-admin/manage-ghes).
|
||||
> The {% data variables.enterprise.management_console %} endpoints will be {% data variables.release-phases.closing_down %} in a future version of {% data variables.product.prodname_ghe_server %}. You can access the same functionality using the Manage {% data variables.product.prodname_ghe_server %} endpoints. For more information, see [AUTOTITLE](/rest/enterprise-admin/manage-ghes).
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -26,4 +26,4 @@ legacy_archived_item_limit: '10,000'
|
||||
issue_type_limit: '25'
|
||||
sub-issue_limit: '100'
|
||||
|
||||
tasklists: 'tasklists (beta)'
|
||||
tasklists: 'tasklists ({% data variables.release-phases.public_preview %})'
|
||||
|
||||
@@ -1,6 +1,8 @@
|
||||
# Contains variables to identify GitHub's release phases. These are aligned with Microsoft standards.
|
||||
# For reference: https://github.com/github/docs-team/issues/4302
|
||||
|
||||
preview: 'preview'
|
||||
|
||||
public_preview: >-
|
||||
{% ifversion ghes < 3.16 %}beta{% else %}public preview{% endif %}
|
||||
|
||||
|
||||
@@ -39,6 +39,7 @@ const EXCLUDED_PATHS: string[] = [
|
||||
'data/reusables/code-scanning/codeql-query-tables/cpp.md',
|
||||
'data/reusables/dependabot/dependabot-updates-supported-versioning-tags.md',
|
||||
'data/variables/release-phases.yml',
|
||||
'data/release-notes/enterprise-server/3-17/0-rc1.yml',
|
||||
// Directories
|
||||
'content/site-policy/',
|
||||
'data/features/',
|
||||
|
||||
Reference in New Issue
Block a user