diff --git a/content/admin/managing-iam/provisioning-user-accounts-with-scim/user-provisioning-with-scim-on-ghes.md b/content/admin/managing-iam/provisioning-user-accounts-with-scim/user-provisioning-with-scim-on-ghes.md index a37dc9597e53..1e90c192a404 100644 --- a/content/admin/managing-iam/provisioning-user-accounts-with-scim/user-provisioning-with-scim-on-ghes.md +++ b/content/admin/managing-iam/provisioning-user-accounts-with-scim/user-provisioning-with-scim-on-ghes.md @@ -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 %}. diff --git a/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/publishing-and-using-codeql-packs.md b/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/publishing-and-using-codeql-packs.md index 6fcf7ae5624a..6a0952b94bf2 100644 --- a/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/publishing-and-using-codeql-packs.md +++ b/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/publishing-and-using-codeql-packs.md @@ -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 diff --git a/content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/using-the-codeql-model-editor.md b/content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/using-the-codeql-model-editor.md index fbf3f6965858..09c52ad99712 100644 --- a/content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/using-the-codeql-model-editor.md +++ b/content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/using-the-codeql-model-editor.md @@ -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. 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. diff --git a/content/code-security/dependabot/working-with-dependabot/dependabot-options-reference.md b/content/code-security/dependabot/working-with-dependabot/dependabot-options-reference.md index 9a22dc0c73d4..97d2c450e448 100644 --- a/content/code-security/dependabot/working-with-dependabot/dependabot-options-reference.md +++ b/content/code-security/dependabot/working-with-dependabot/dependabot-options-reference.md @@ -828,6 +828,8 @@ New version `2.0.0` ### Versioning tags + + * 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. + + {% endif %} ## Top-level `registries` key diff --git a/content/copilot/how-tos/use-copilot-for-common-tasks/index.md b/content/copilot/how-tos/use-copilot-for-common-tasks/index.md index 45e491ab47a5..eb572de16542 100644 --- a/content/copilot/how-tos/use-copilot-for-common-tasks/index.md +++ b/content/copilot/how-tos/use-copilot-for-common-tasks/index.md @@ -7,7 +7,7 @@ versions: topics: - Copilot children: - - /use-copilot-to-create-issues + - /use-copilot-to-create-or-update-issues - /create-a-pr-summary - /use-copilot-in-the-cli redirect_from: diff --git a/content/copilot/how-tos/use-copilot-for-common-tasks/use-copilot-in-the-cli.md b/content/copilot/how-tos/use-copilot-for-common-tasks/use-copilot-in-the-cli.md index 3a49e7af566e..90e867ad88a6 100644 --- a/content/copilot/how-tos/use-copilot-for-common-tasks/use-copilot-in-the-cli.md +++ b/content/copilot/how-tos/use-copilot-for-common-tasks/use-copilot-in-the-cli.md @@ -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). diff --git a/content/copilot/how-tos/use-copilot-for-common-tasks/use-copilot-to-create-issues.md b/content/copilot/how-tos/use-copilot-for-common-tasks/use-copilot-to-create-or-update-issues.md similarity index 79% rename from content/copilot/how-tos/use-copilot-for-common-tasks/use-copilot-to-create-issues.md rename to content/copilot/how-tos/use-copilot-for-common-tasks/use-copilot-to-create-or-update-issues.md index 14009fd2f8c6..a171765720c2 100644 --- a/content/copilot/how-tos/use-copilot-for-common-tasks/use-copilot-to-create-issues.md +++ b/content/copilot/how-tos/use-copilot-for-common-tasks/use-copilot-to-create-or-update-issues.md @@ -1,10 +1,10 @@ --- -title: Using GitHub Copilot to create issues -shortTitle: Use Copilot to create issues -intro: 'Use {% data variables.product.prodname_copilot_short %} to quickly generate structured, high-quality issues from natural language or images, without filling out every field manually.' -permissions: 'Anyone with a {% data variables.product.prodname_copilot_short %} license can use {% data variables.product.prodname_copilot_short %} to create issues.
Try {% data variables.product.prodname_copilot_short %} for free {% octicon "link-external" height:16 %}' +title: Using GitHub Copilot to create or update issues +shortTitle: Use Copilot to create or update issues +intro: Use {% data variables.product.prodname_copilot_short %} to quickly generate structured, high-quality issues from natural language or images, without filling out every field manually. +permissions: Anyone with a {% data variables.product.prodname_copilot_short %} license can use {% data variables.product.prodname_copilot_short %} to create issues or update existing issues.
Try {% data variables.product.prodname_copilot_short %} for free {% octicon "link-external" height:16 %} versions: - feature: copilot + feature: copilot-create-issues topics: - Copilot - Issues @@ -13,17 +13,18 @@ redirect_from: - /copilot/using-github-copilot/using-github-copilot-to-create-issues - /copilot/how-tos/github-flow/using-github-copilot-to-create-issues - /copilot/how-tos/github-flow/use-copilot-to-create-issues + - /copilot/how-tos/use-copilot-for-common-tasks/use-copilot-to-create-issues contentType: how-tos -category: +category: - Author and optimize with Copilot --- > [!NOTE] > This feature is in {% data variables.release-phases.public_preview %} and subject to change. -Creating issues manually can be repetitive and time-consuming. With {% data variables.product.prodname_copilot_short %}, you can create issues faster by prompting in natural language, or even by uploading a screenshot. {% data variables.product.prodname_copilot_short %} fills out the title, body, labels, assignees, and more, using your repository’s issue forms or templates. +Creating or updating issues manually can be repetitive and time-consuming. With {% data variables.product.prodname_copilot_short %}, you can create or update issues faster by prompting in natural language, or even by uploading a screenshot. {% data variables.product.prodname_copilot_short %} fills out the title, body, labels, assignees, and more, using your repository’s issue forms or templates. -You stay in control of the process. You can review and refine what {% data variables.product.prodname_copilot_short %} suggests before you submit the new issue. +You stay in control of the process. You can review and refine what {% data variables.product.prodname_copilot_short %} suggests before you submit the new or updated issue. ## Creating an issue with {% data variables.product.prodname_copilot_short %} @@ -88,26 +89,36 @@ For example: {% data variables.product.prodname_copilot_short %} generates a draft issue tree, with a parent issue at the top level and sub-issues beneath it. -You can review the issue tree, expand or collapse sub-issues, and edit the details of each issue. +You can review the issue tree, expand or collapse sub-issues, and edit the details of each issue. Click the parent issue to view its details in the workbench. The parent issue displays a list of sub-issues, and you can click each one to view and edit its details in the workbench. From a sub-issue, use the "Parent" dropdown to navigate through the issue tree. You can also click **Review and create** at the top of the workbench to see the full issue tree and navigate directly to any issue. {% data variables.product.prodname_copilot_short %} can modify the tree, by unlinking issues or by attaching new drafts. For example, you can: -* Remove a sub-issue from the issue tree: +* Remove a sub-issue from the issue tree: `Remove sub-issue NAME_OF_ISSUE from the issue tree` * Add an additional sub-issue to the issue tree: `Add an additional sub-issue with ISSUE_DETAILS to the issue tree` Once you've finished editing the drafts and are ready to publish the issues, click **Review and create** then click **Create issues**. -## Working with existing issues +## Updating an existing issue + +You can use {% data variables.product.prodname_copilot_short %} to update existing issues in your repository. + +For example: + +`In octo-org/octo-repo, update issue #123 to add more details about the bug and steps to reproduce it. Also, change the label to "bug" and assign it to @username.` + +{% data variables.product.prodname_copilot_short %} drafts the updated issue, which you can review and edit in the workbench. To publish the changes, click **Update**. + +## Working with existing parent issues and sub-issues You can use {% data variables.product.prodname_copilot_short %} to connect new issues with issues that already exist in your repository. For example, you can: -* Add a sub-issue to an existing parent issue: +* Add a sub-issue to an existing parent issue: `Create a sub-issue for octo-org/octo-repo issue #456.` * Add a parent issue to an existing issue: `Create a parent issue for octo-org/octo-repo issue #456.` diff --git a/content/copilot/tutorials/enhance-agent-mode-with-mcp.md b/content/copilot/tutorials/enhance-agent-mode-with-mcp.md index fc6dbc8da956..e531aa0be1aa 100644 --- a/content/copilot/tutorials/enhance-agent-mode-with-mcp.md +++ b/content/copilot/tutorials/enhance-agent-mode-with-mcp.md @@ -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). diff --git a/content/copilot/tutorials/plan-a-project.md b/content/copilot/tutorials/plan-a-project.md index 4711fe23fb88..8d462d06e531 100644 --- a/content/copilot/tutorials/plan-a-project.md +++ b/content/copilot/tutorials/plan-a-project.md @@ -53,7 +53,7 @@ With the repository set up, you can use {% data variables.product.prodname_copil ### Create an epic issue -1. Enter a detailed project description as your prompt. For example: +1. Enter a detailed project description as your prompt. For example: ```I’m planning to create a shopping website in React and Node.js. The site should allow users to browse products by category, search for items, add products to a cart, and complete checkout. Please help me plan the project by creating issues and breaking it down into epics, features, and tasks.``` 1. Submit your prompt. {% data variables.product.prodname_copilot_short %} will generate an issue tree, typically with an epic at the top and sub-issues for each main feature or task @@ -62,14 +62,14 @@ With the repository set up, you can use {% data variables.product.prodname_copil ## Navigate the issue tree 1. Click the epic to view its details in the workbench. Navigate through the workbench to explore the issue tree. -1. Each issue typically includes a title and description. Additional metadata such as labels or assignees, can be edited directly in the workbench. +1. Each issue typically includes a title and description. Additional metadata such as labels or assignees, can be edited directly in the workbench. 1. You can expand or collapse sub-issues to focus on specific parts of the project. The issue tree provides a clear overview of your project structure, making it easy to navigate between epics, features, and tasks. 1. In this first iteration of the draft, {% data variables.product.prodname_copilot_short %} may generate only high-level issues. You can refine these issues further by breaking them down into smaller tasks or features. Let's refine the issue "Feature: UI Skeleton and Navigation". - Prompt {% data variables.product.prodname_copilot_short %} with: + Prompt {% data variables.product.prodname_copilot_short %} with: ```Can you break down the issue "Feature: UI Skeleton and Navigation" into smaller tasks?``` {% data variables.product.prodname_copilot_short %} will generate multiple new sub-issues such as: @@ -79,7 +79,7 @@ With the repository set up, you can use {% data variables.product.prodname_copil * Task: Integrate navigation with routing * Task: Add basic responsive layout -1. Repeat this process for the remaining feature issues in the epic. +1. Repeat this process for the remaining feature issues in the epic. ![Screenshot of the Copilot Chat workbench. The workbench displays an issue tree with an epic at the top and several sub-issues beneath it.](/assets/images/help/copilot/copilot-creates-sub-issues-workbench.png) @@ -87,12 +87,12 @@ With the repository set up, you can use {% data variables.product.prodname_copil After you finish generating the issue tree you may notice that {% data variables.product.prodname_copilot_short %}’s issue descriptions may be brief or unclear. To make them actionable, refine each issue as needed. -1. Start with the newly generated issue such as "Task: Create placeholder pages for main routes". +1. Start with the newly generated issue such as "Task: Create placeholder pages for main routes". - Prompt {% data variables.product.prodname_copilot_short %} with: + Prompt {% data variables.product.prodname_copilot_short %} with: ```Can you improve the description for “Task: Create placeholder pages for main routes”? Please provide a detailed technical summary, list the main routes to be included, outline the steps for implementation, and specify what should be delivered for this task. Please add any relevant code snippets.``` -1. {% data variables.product.prodname_copilot_short %} will generate a new version of the draft issue "Task: Create placeholder pages for main routes." +1. {% data variables.product.prodname_copilot_short %} will generate a new version of the draft issue "Task: Create placeholder pages for main routes." At the top-left of the issue, click the versioning drop-down and select **Version 2** to review the new changes. 1. Review and decide whether to keep {% data variables.product.prodname_copilot_short %}’s revised version, edit further, or prompt again for more detail. {% data variables.product.prodname_copilot_short %} can add code snippets into the draft to improve clarity and provide immediate context for these issues. @@ -112,7 +112,7 @@ Now that you’ve generated and refined your project issues, you can assign them ## Further reading -* [AUTOTITLE](/copilot/how-tos/use-copilot-for-common-tasks/use-copilot-to-create-issues) +* [AUTOTITLE](/copilot/how-tos/use-copilot-for-common-tasks/use-copilot-to-create-or-update-issues) * [AUTOTITLE](/copilot/tutorials/coding-agent/pilot-coding-agent) * [AUTOTITLE](/copilot/tutorials/coding-agent/get-the-best-results) * [AUTOTITLE](/copilot/tutorials/speed-up-development-work) diff --git a/content/enterprise-onboarding/support-for-your-enterprise/understanding-support.md b/content/enterprise-onboarding/support-for-your-enterprise/understanding-support.md index 0f23961dd7da..1158e3e63d06 100644 --- a/content/enterprise-onboarding/support-for-your-enterprise/understanding-support.md +++ b/content/enterprise-onboarding/support-for-your-enterprise/understanding-support.md @@ -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 %}: diff --git a/content/get-started/git-basics/ignoring-files.md b/content/get-started/git-basics/ignoring-files.md index cd15f1246393..3bba3c400c42 100644 --- a/content/get-started/git-basics/ignoring-files.md +++ b/content/get-started/git-basics/ignoring-files.md @@ -17,7 +17,7 @@ versions: ## Configuring ignored files for a single repository You can create a `.gitignore` file in your repository's root directory to tell Git which files and directories to ignore when you make a commit. -To share the ignore rules with other users who clone the repository, commit the `.gitignore` file in to your repository. +To share the ignore rules with other users who clone the repository, commit the `.gitignore` file into your repository. GitHub maintains an official list of recommended `.gitignore` files for many popular operating systems, environments, and languages in the "github/gitignore" public repository. You can also use gitignore.io to create a `.gitignore` file for your operating system, programming language, or IDE. For more information, see [github/gitignore](https://github.com/github/gitignore) and the [gitignore.io](https://www.gitignore.io/) site. diff --git a/content/integrations/how-tos/slack/customize-notifications.md b/content/integrations/how-tos/slack/customize-notifications.md index 8970fe16f375..e86ea1de07e3 100644 --- a/content/integrations/how-tos/slack/customize-notifications.md +++ b/content/integrations/how-tos/slack/customize-notifications.md @@ -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 diff --git a/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md b/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md index ea42d6755641..ccbf6a9cb8bf 100644 --- a/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md +++ b/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md @@ -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**. - ![Screenshot of the list of milestones. Within the entry for the "beta release" milestone, a link, labeled "Edit," is outlined in dark orange.](/assets/images/help/repository/edit-milestone.png) + ![Screenshot of the list of milestones. Within the entry for the "beta release" milestone, a link, labeled "Edit," is outlined in dark orange.](/assets/images/help/repository/edit-milestone.png) 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**. -![Screenshot of the list of milestones for a repository. Within the entry for the "beta release" milestone, a red "Delete" link is outlined in orange.](/assets/images/help/repository/delete-milestone.png) +![Screenshot of the list of milestones for a repository. Within the entry for the "beta release" milestone, a red "Delete" link is outlined in orange.](/assets/images/help/repository/delete-milestone.png) diff --git a/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md b/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md index 0095e3c82bdf..37d910a416be 100644 --- a/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md +++ b/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md @@ -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. + + ```shell gh release create v1.3.2 --title "v1.3.2 (beta)" --notes "this is a {% data variables.release-phases.public_preview %} release" --prerelease ``` + + 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 %} diff --git a/data/features/copilot-create-issues.yml b/data/features/copilot-create-issues.yml new file mode 100644 index 000000000000..3b5d9f0653d4 --- /dev/null +++ b/data/features/copilot-create-issues.yml @@ -0,0 +1,7 @@ +# Reference: #19182 +# Copilot create issues public beta + +versions: + fpt: '*' + ghec: '*' + ghes: '>= 3.20' diff --git a/data/release-notes/enterprise-server/3-16/0-rc1.yml b/data/release-notes/enterprise-server/3-16/0-rc1.yml index b4c86a63caf4..5b9b38884800 100644 --- a/data/release-notes/enterprise-server/3-16/0-rc1.yml +++ b/data/release-notes/enterprise-server/3-16/0-rc1.yml @@ -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/). diff --git a/data/release-notes/enterprise-server/3-16/0.yml b/data/release-notes/enterprise-server/3-16/0.yml index de3361278b14..ebcf5ce8e53f 100644 --- a/data/release-notes/enterprise-server/3-16/0.yml +++ b/data/release-notes/enterprise-server/3-16/0.yml @@ -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: - | diff --git a/data/release-notes/enterprise-server/3-17/3.yml b/data/release-notes/enterprise-server/3-17/3.yml index 2a8b9c19f2ce..3980717374c8 100644 --- a/data/release-notes/enterprise-server/3-17/3.yml +++ b/data/release-notes/enterprise-server/3-17/3.yml @@ -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`. diff --git a/data/release-notes/enterprise-server/3-18/0-rc1.yml b/data/release-notes/enterprise-server/3-18/0-rc1.yml index b7fe2e86b4fc..7f99063c7b1e 100644 --- a/data/release-notes/enterprise-server/3-18/0-rc1.yml +++ b/data/release-notes/enterprise-server/3-18/0-rc1.yml @@ -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). \ No newline at end of file + 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). \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-18/0.yml b/data/release-notes/enterprise-server/3-18/0.yml index 7be8140a0915..704fb14e9116 100644 --- a/data/release-notes/enterprise-server/3-18/0.yml +++ b/data/release-notes/enterprise-server/3-18/0.yml @@ -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). diff --git a/data/reusables/actions/workflows/run-on-specific-branches-or-tags3.md b/data/reusables/actions/workflows/run-on-specific-branches-or-tags3.md index f17c333a32d4..f074e757c9d2 100644 --- a/data/reusables/actions/workflows/run-on-specific-branches-or-tags3.md +++ b/data/reusables/actions/workflows/run-on-specific-branches-or-tags3.md @@ -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`) * A tag named `v2` (`refs/tags/v2`) * A tag whose name starts with `v1.`, like `v1.9` (`refs/tags/v1.9`) diff --git a/data/reusables/actions/workflows/run-on-specific-branches-or-tags4.md b/data/reusables/actions/workflows/run-on-specific-branches-or-tags4.md index 994269522990..e4f0c56fd2da 100644 --- a/data/reusables/actions/workflows/run-on-specific-branches-or-tags4.md +++ b/data/reusables/actions/workflows/run-on-specific-branches-or-tags4.md @@ -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. ```yaml on: diff --git a/data/reusables/actions/workflows/section-specifying-branches.md b/data/reusables/actions/workflows/section-specifying-branches.md index 2107a3329f6e..baa7a1aae482 100644 --- a/data/reusables/actions/workflows/section-specifying-branches.md +++ b/data/reusables/actions/workflows/section-specifying-branches.md @@ -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`. ```yaml on: diff --git a/data/reusables/actions/workflows/triggering-workflow-branches3.md b/data/reusables/actions/workflows/triggering-workflow-branches3.md index 0e7d8670ca24..96515a6de715 100644 --- a/data/reusables/actions/workflows/triggering-workflow-branches3.md +++ b/data/reusables/actions/workflows/triggering-workflow-branches3.md @@ -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`) ```yaml on: diff --git a/data/reusables/actions/workflows/triggering-workflow-branches4.md b/data/reusables/actions/workflows/triggering-workflow-branches4.md index c75a7b01ed5c..ebe6fc8ddef5 100644 --- a/data/reusables/actions/workflows/triggering-workflow-branches4.md +++ b/data/reusables/actions/workflows/triggering-workflow-branches4.md @@ -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. ```yaml on: diff --git a/data/reusables/enterprise_management_console/api-deprecation.md b/data/reusables/enterprise_management_console/api-deprecation.md index 74b8b6790b2b..0e98ce5f43b9 100644 --- a/data/reusables/enterprise_management_console/api-deprecation.md +++ b/data/reusables/enterprise_management_console/api-deprecation.md @@ -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 %} diff --git a/data/variables/projects.yml b/data/variables/projects.yml index cca4335d8314..46dd29b338e9 100644 --- a/data/variables/projects.yml +++ b/data/variables/projects.yml @@ -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 %})' diff --git a/data/variables/release-phases.yml b/data/variables/release-phases.yml index d25cf4150bea..8d82589157bd 100644 --- a/data/variables/release-phases.yml +++ b/data/variables/release-phases.yml @@ -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 %} diff --git a/src/content-linter/lib/linting-rules/outdated-release-phase-terminology.ts b/src/content-linter/lib/linting-rules/outdated-release-phase-terminology.ts index d2f457f528b7..cff7228581a2 100644 --- a/src/content-linter/lib/linting-rules/outdated-release-phase-terminology.ts +++ b/src/content-linter/lib/linting-rules/outdated-release-phase-terminology.ts @@ -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/', diff --git a/src/data-directory/lib/data-schemas/index.ts b/src/data-directory/lib/data-schemas/index.ts index 3b5fd19d245e..68753e47265d 100644 --- a/src/data-directory/lib/data-schemas/index.ts +++ b/src/data-directory/lib/data-schemas/index.ts @@ -8,6 +8,21 @@ interface DataSchemas { [key: string]: string } +// Helper function to resolve schema paths based on runtime context +function resolveSchemaPath(filename: string): string { + // Check if we're in a test context + const isTest = process.env.NODE_ENV === 'test' + + if (isTest) { + // Use relative paths that work for vitest and 4.x compatibility with + // dynamic imports in particular + return `../lib/data-schemas/${filename}` + } else { + // Use absolute paths that work for content linter and other contexts + return `@/data-directory/lib/data-schemas/${filename}` + } +} + // Auto-discover table schemas from data/tables/ directory function loadTableSchemas(): DataSchemas { const tablesDir = path.join(process.cwd(), 'data/tables') @@ -22,8 +37,8 @@ function loadTableSchemas(): DataSchemas { const schemaPath = path.join(schemasDir, `${name}.ts`) if (fs.existsSync(schemaPath)) { - // Use relative path from test file for vitest 4.x compatibility with dynamic imports - tableSchemas[`data/tables/${yamlFile}`] = `../lib/data-schemas/tables/${name}.ts` + // Use the resolver for consistent path handling + tableSchemas[`data/tables/${yamlFile}`] = resolveSchemaPath(`tables/${name}.ts`) } } } @@ -32,15 +47,14 @@ function loadTableSchemas(): DataSchemas { } // Manual schema registrations for non-table data -// Use relative paths from the test file for vitest 4.x compatibility with dynamic imports const manualSchemas: DataSchemas = { - 'data/features': '../lib/data-schemas/features.ts', - 'data/variables': '../lib/data-schemas/variables.ts', - 'data/learning-tracks': '../lib/data-schemas/learning-tracks.ts', - 'data/release-notes': '../lib/data-schemas/release-notes.ts', - 'data/code-languages.yml': '../lib/data-schemas/code-languages.ts', - 'data/glossaries/candidates.yml': '../lib/data-schemas/glossaries-candidates.ts', - 'data/glossaries/external.yml': '../lib/data-schemas/glossaries-external.ts', + 'data/features': resolveSchemaPath('features.ts'), + 'data/variables': resolveSchemaPath('variables.ts'), + 'data/learning-tracks': resolveSchemaPath('learning-tracks.ts'), + 'data/release-notes': resolveSchemaPath('release-notes.ts'), + 'data/code-languages.yml': resolveSchemaPath('code-languages.ts'), + 'data/glossaries/candidates.yml': resolveSchemaPath('glossaries-candidates.ts'), + 'data/glossaries/external.yml': resolveSchemaPath('glossaries-external.ts'), } // Combine manual registrations with auto-discovered table schemas