From 8427e03b79314391d5b691a1b5e1a24f45944dca Mon Sep 17 00:00:00 2001 From: Copilot <198982749+Copilot@users.noreply.github.com> Date: Thu, 9 Jul 2026 12:20:25 +1000 Subject: [PATCH 01/17] =?UTF-8?q?Rework=20=E2=80=9CAbout=20GitHub=20and=20?= =?UTF-8?q?Git=E2=80=9D=20into=20=E2=80=9CWhat=20is=20GitHub=3F=E2=80=9D?= =?UTF-8?q?=20and=20repoint=20inbound=20docs=20links=20(#62184)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: Vanessa Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- content/get-started/index.md | 2 +- .../about-github-and-git.md | 80 ------------------- .../get-started/start-your-journey/index.md | 4 +- .../start-your-journey/what-is-github.md | 71 ++++++++++++++++ .../using-github-docs/github-docs-api.md | 8 +- .../repositories/importing-context.md | 2 +- 6 files changed, 79 insertions(+), 88 deletions(-) delete mode 100644 content/get-started/start-your-journey/about-github-and-git.md create mode 100644 content/get-started/start-your-journey/what-is-github.md diff --git a/content/get-started/index.md b/content/get-started/index.md index 3ed2a442ebb1..a1e9db8470fd 100644 --- a/content/get-started/index.md +++ b/content/get-started/index.md @@ -27,7 +27,7 @@ versions: layout: discovery-landing introLinks: quickstart: /get-started/start-your-journey/hello-world - overview: /get-started/start-your-journey/about-github-and-git + overview: /get-started/start-your-journey/what-is-github carousels: recommended: - /get-started/start-your-journey diff --git a/content/get-started/start-your-journey/about-github-and-git.md b/content/get-started/start-your-journey/about-github-and-git.md deleted file mode 100644 index 5aa709d4835d..000000000000 --- a/content/get-started/start-your-journey/about-github-and-git.md +++ /dev/null @@ -1,80 +0,0 @@ ---- -title: About GitHub and Git -shortTitle: About GitHub and Git -intro: You can use {% data variables.product.github %} and Git to collaborate on work. -versions: - fpt: '*' - ghes: '*' - ghec: '*' -redirect_from: - - /get-started/quickstart/about-github-and-git -category: - - Set up your account on GitHub -contentType: concepts ---- - -## About {% data variables.product.github %} - -{% data variables.product.github %} is a {% ifversion not ghes %}cloud-based {% endif %}platform where you can store, share, and work together with others to write code. - -Storing your code in a "repository" on {% data variables.product.github %} allows you to: -* **Showcase or share** your work. -* **Track and manage** changes to your code over time. -* Let others **review** your code, and make suggestions to improve it. -* **Collaborate** on a shared project, without worrying that your changes will impact the work of your collaborators before you're ready to integrate them. - -Collaborative working, one of {% data variables.product.github %}’s fundamental features, is made possible by the open-source software, Git, upon which {% data variables.product.github %} is built. - -## About Git - -Git is a version control system that intelligently tracks changes in files. Git is particularly useful when you and a group of people are all making changes to the same files at the same time. - -Typically, to do this in a Git-based workflow, you would: -* **Create a branch** off from the main copy of files that you (and your collaborators) are working on. -* **Make edits** to the files independently and safely on your own personal branch. -* Let Git intelligently **merge** your specific changes back into the main copy of files, so that your changes don't impact other people's updates. -* Let Git **keep track** of your and other people's changes, so you all stay working on the most up-to-date version of the project. - -{% ifversion fpt %} -To try using Git yourself, see [AUTOTITLE](/get-started/learning-to-code/getting-started-with-git). -{% else %} -If you want to learn more about Git, see [AUTOTITLE](/get-started/using-git/about-git). -{% endif %} - -### How do Git and {% data variables.product.github %} work together? - -When you upload files to {% data variables.product.github %}, you'll store them in a "Git repository." This means that when you make changes (or "commits") to your files in {% data variables.product.github %}, Git will automatically start to track and manage your changes. - -There are plenty of Git-related actions that you can complete on {% data variables.product.github %} directly in your browser, such as creating a Git repository, creating branches, and uploading and editing files. - -However, most people work on their files locally (on their own computer), then continually sync these local changes—and all the related Git data—with the central "remote" repository on {% data variables.product.github %}. There are plenty of tools that you can use to do this, such as GitHub Desktop. - -Once you start to collaborate with others and all need to work on the same repository at the same time, you’ll continually: - -* **Pull** all the latest changes made by your collaborators from the remote repository on {% data variables.product.github %}. -* **Push** back your own changes to the same remote repository on {% data variables.product.github %}. - -Git figures out how to intelligently merge this flow of changes, and {% data variables.product.github %} helps you manage the flow through features such as "pull requests." - -## Where do I start? - -If you're new to {% data variables.product.github %}, and unfamiliar with Git, we recommend working through the articles in the [AUTOTITLE](/get-started/start-your-journey) category. The articles focus on tasks you can complete directly in your browser on {% data variables.product.github %} and will help you to: - -* **Create an account** on {% data variables.product.github %}. -* **Learn the "{% data variables.product.github %} Flow"**, and the key principles of collaborative working (branches, commits, pull requests, merges). -* **Personalise your profile** to share your interests and skills. -* **Explore {% data variables.product.github %}** to find inspiration for your own projects and connect with others. -* Learn how to **download** interesting code for your own use. -* Learn how to **upload** something you're working on to a {% data variables.product.github %} repository. - -{% ifversion fpt or ghec %} - -## Next steps - -* [AUTOTITLE](/get-started/start-your-journey/creating-an-account-on-github) - -{% endif %} - -## Further reading - -* [AUTOTITLE](/get-started/using-github/connecting-to-github) diff --git a/content/get-started/start-your-journey/index.md b/content/get-started/start-your-journey/index.md index a13fd707f440..7ece3a127f89 100644 --- a/content/get-started/start-your-journey/index.md +++ b/content/get-started/start-your-journey/index.md @@ -6,7 +6,7 @@ versions: ghes: '*' ghec: '*' children: - - /about-github-and-git + - /what-is-github - /creating-an-account-on-github - /hello-world - /setting-up-your-profile @@ -23,7 +23,7 @@ journeyTracks: title: 'Get started' description: 'Master the fundamentals of {% data variables.product.github %} and Git.' guides: - - href: '/get-started/start-your-journey/about-github-and-git' + - href: '/get-started/start-your-journey/what-is-github' - href: '/get-started/start-your-journey/creating-an-account-on-github' - href: '/get-started/start-your-journey/hello-world' - href: '/get-started/start-your-journey/setting-up-your-profile' diff --git a/content/get-started/start-your-journey/what-is-github.md b/content/get-started/start-your-journey/what-is-github.md new file mode 100644 index 000000000000..79c108f7667a --- /dev/null +++ b/content/get-started/start-your-journey/what-is-github.md @@ -0,0 +1,71 @@ +--- +title: What is GitHub? +shortTitle: What is GitHub? +intro: '{% data variables.product.github %} is a platform that supports your entire software development process, from planning work to deploying and operating software.' +versions: + fpt: '*' + ghes: '*' + ghec: '*' +redirect_from: + - /get-started/quickstart/about-github-and-git + - /get-started/start-your-journey/about-github-and-git +category: + - Set up your account on GitHub +contentType: concepts +--- + +{% data variables.product.github %} is a platform for building software. Whether you are starting a new project or contributing to an existing one, {% data variables.product.github %} brings together the tools and workflows you need across every stage of the software development life cycle (SDLC). + +## {% data variables.product.github %} and the software development life cycle + +The software development life cycle describes the stages a software project moves through, from the first idea to running code in production. {% data variables.product.github %} is designed to support every stage of that process. + +| Stage | What you can do on {% data variables.product.github %} | +|---|---| +| Plan | Track your work, set milestones, and organize long-term projects. | +| Create | Write and store code, develop new features safely, and create a clear timeline of your changes. | +| Review | Suggest changes to your project, discuss your updates with reviewers, and apply feedback. | +| Test | Automate checks to validate every change before it merges. | +| Deploy | Ship software with automated deployment workflows and release management. | +| Operate | Monitor applications, manage dependencies, and find and fix security issues. | + +You do not need to use every stage at once. Many people start with a repository and a few issues, then expand their use of the platform as their project grows. + +## {% data variables.product.github %} and Git + +{% data variables.product.github %} is based on the open-source software, Git. + +Git is a version control system that tracks changes to files. It lets you work on your own copy of a project, record a history of your changes, and merge your work with other people's changes safely. + +{% data variables.product.github %} builds on Git by hosting your Git projects, called **repositories**, in the cloud, as well as adding planning and collaboration tools that make it easier for teams to work together. + +For more information about Git, see [AUTOTITLE](/get-started/using-git/about-git). + +## Is {% data variables.product.github %} right for me? + +{% data variables.product.github %} is used by students, developers, project managers, security teams, data scientists, researchers, human resources and legal staff, and many others across organizations of all sizes. + +Some of the most common reasons people use {% data variables.product.github %} are: + +* Store and manage code with version control. +* Write code, review code, manage security vulnerabilities and updates. +* Collaborate and socialize on projects. +* Contribute to open source software. +* Issue tracking and project management. +* Automate software development workflows like CI/CD, testing, and deployments. +* Showcase and share work. +* Publish and release software packages. +* Host documentation and websites. +* Participate in software development communities and discussions. +* Use AI-powered tools and agents to help write, understand, review, and automate code development faster. + +## Where do I start? + +If you're new to {% data variables.product.github %} and unfamiliar with Git, we recommend working through the articles in the [AUTOTITLE](/get-started/start-your-journey) category. The articles show you how to perform common tasks software developers do using {% data variables.product.github %}, such as: + +* **Create a project** and store the code on {% data variables.product.github %}. +* **Plan your work** by creating issues and tracking your project work. +* **Connect to your project on your local machine** and use the {% data variables.product.prodname_desktop %} application to manage code changes with Git. +* **Update your project code**, optionally pair with an AI assistant, and sync your changes with {% data variables.product.github %}. +* **Review your proposed code changes** by creating pull requests and reviewing your own changes before you merge. +* **Deploy your project** using automated deployment workflows, allowing you to publish a basic website. diff --git a/content/get-started/using-github-docs/github-docs-api.md b/content/get-started/using-github-docs/github-docs-api.md index 188d9c486871..d5736b11d666 100644 --- a/content/get-started/using-github-docs/github-docs-api.md +++ b/content/get-started/using-github-docs/github-docs-api.md @@ -20,7 +20,7 @@ The Article endpoint returns the Markdown content and metadata of any {% data va The Article endpoint accepts the following query parameter: * `pathname` (required): The article path, including a language prefix such as `/en/` or `/ja/`. - * For example, `/en/get-started/start-your-journey/about-github-and-git`. + * For example, `/en/get-started/start-your-journey/what-is-github`. In addition, `GET /api/article` and `GET /api/article/body` accept the following optional query parameter: @@ -31,7 +31,7 @@ In addition, `GET /api/article` and `GET /api/article/body` accept the following `GET https://docs.github.com/api/article/body` returns the full article content as Markdown. ```shell -curl "https://docs.github.com/api/article/body?pathname=/en/get-started/start-your-journey/about-github-and-git" +curl "https://docs.github.com/api/article/body?pathname=/en/get-started/start-your-journey/what-is-github" ``` To access a versioned article (for example, for {% data variables.product.prodname_ghe_cloud %}), include the version in the path: @@ -45,7 +45,7 @@ curl "https://docs.github.com/api/article/body?pathname=/en/enterprise-cloud@lat `GET https://docs.github.com/api/article/meta` returns metadata about an article as JSON, including the title, intro, product area, document type, and breadcrumbs. ```shell -curl "https://docs.github.com/api/article/meta?pathname=/en/get-started/start-your-journey/about-github-and-git" +curl "https://docs.github.com/api/article/meta?pathname=/en/get-started/start-your-journey/what-is-github" ``` ### Getting content and metadata together @@ -53,7 +53,7 @@ curl "https://docs.github.com/api/article/meta?pathname=/en/get-started/start-yo `GET https://docs.github.com/api/article` returns both metadata and the article body in a single JSON response, combining the results of the body and meta endpoints. ```shell -curl "https://docs.github.com/api/article?pathname=/en/get-started/start-your-journey/about-github-and-git" +curl "https://docs.github.com/api/article?pathname=/en/get-started/start-your-journey/what-is-github" ``` ## Pagelist endpoint diff --git a/data/reusables/repositories/importing-context.md b/data/reusables/repositories/importing-context.md index 6391b6407132..b70a02d19260 100644 --- a/data/reusables/repositories/importing-context.md +++ b/data/reusables/repositories/importing-context.md @@ -1 +1 @@ -Importing your source code to {% data variables.product.prodname_dotcom %} makes it easier for you and others to work together on projects and manage code. {% data variables.product.prodname_dotcom %} helps you collaborate, track changes, and organize tasks, making it simpler to build and manage projects. For more information, see [AUTOTITLE](/get-started/start-your-journey/about-github-and-git). +Importing your source code to {% data variables.product.prodname_dotcom %} makes it easier for you and others to work together on projects and manage code. {% data variables.product.prodname_dotcom %} helps you collaborate, track changes, and organize tasks, making it simpler to build and manage projects. For more information, see [AUTOTITLE](/get-started/start-your-journey/what-is-github). From 6ed5ec8f1b5f652b9156eba8513b1a7d1bb051ef Mon Sep 17 00:00:00 2001 From: Copilot <198982749+Copilot@users.noreply.github.com> Date: Thu, 9 Jul 2026 14:49:50 +1000 Subject: [PATCH 02/17] llms-txt: update curl examples to use what-is-github slug (#62185) Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: vgrl <25145994+vgrl@users.noreply.github.com> Co-authored-by: Vanessa --- data/llms-txt/config-default.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/data/llms-txt/config-default.yml b/data/llms-txt/config-default.yml index 9f07eacf23b0..75cd578ae5bb 100644 --- a/data/llms-txt/config-default.yml +++ b/data/llms-txt/config-default.yml @@ -11,8 +11,8 @@ how_to_use: | * [Versions API](https://docs.github.com/api/pagelist/versions): Lists all available documentation versions. * [Languages API](https://docs.github.com/api/pagelist/languages): Lists all available languages. * [Page List API](https://docs.github.com/api/pagelist/en/free-pro-team@latest): Returns every docs page path for a given language and version. - * [Article API](https://docs.github.com/api/article): Returns the full rendered content and context of any docs page as JSON. Example: `curl "https://docs.github.com/api/article?pathname=/en/get-started/start-your-journey/about-github-and-git"` - * [Article Body API](https://docs.github.com/api/article/body): Returns the full rendered content of any docs page as markdown. Example: `curl "https://docs.github.com/api/article/body?pathname=/en/get-started/start-your-journey/about-github-and-git"` + * [Article API](https://docs.github.com/api/article): Returns the full rendered content and context of any docs page as JSON. Example: `curl "https://docs.github.com/api/article?pathname=/en/get-started/start-your-journey/what-is-github"` + * [Article Body API](https://docs.github.com/api/article/body): Returns the full rendered content of any docs page as markdown. Example: `curl "https://docs.github.com/api/article/body?pathname=/en/get-started/start-your-journey/what-is-github"` * [Search API](https://docs.github.com/api/search/v1): Search across all docs content. Example: `curl "https://docs.github.com/api/search/v1?query=actions&language=en&version=free-pro-team@latest"` * [GitHub MCP server](https://github.com/github/github-mcp-server): For agents that connect via Model Context Protocol, the GitHub MCP server provides tools for working with GitHub itself: repositories, issues, pull requests, workflows, and code. It does not currently include docs search. From f0b469fd8801bdd0053b9dd6fc0f5cbe972d8586 Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Thu, 9 Jul 2026 13:26:00 +0000 Subject: [PATCH 03/17] Bump github/gh-base-image/gh-base-noble from 20260706-152702-gdb3226338 to 20260708-113537-g661fe65de in the baseimages group (#62196) Signed-off-by: dependabot[bot] Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> --- Dockerfile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Dockerfile b/Dockerfile index efe89c333620..4588162de93a 100644 --- a/Dockerfile +++ b/Dockerfile @@ -10,7 +10,7 @@ # --------------------------------------------------------------- # To update the sha: # https://github.com/github/gh-base-image/pkgs/container/gh-base-image%2Fgh-base-noble -FROM ghcr.io/github/gh-base-image/gh-base-noble:20260706-152702-gdb3226338@sha256:badfd5ddfbea7896bb84dbfc20ae326234fa1cc580bb723458158e8a59cf17ec AS base +FROM ghcr.io/github/gh-base-image/gh-base-noble:20260708-113537-g661fe65de@sha256:894162a6b21fc03da8ba889760592e6e223ba76f3067723f93bd1e49aff1c46b AS base # Install curl for Node install and determining the early access branch # Install git for cloning docs-early-access & translations repos From d0f8d21954d0aa1d417a5903ecad196a85270a49 Mon Sep 17 00:00:00 2001 From: Kevin Heis Date: Thu, 9 Jul 2026 06:40:36 -0700 Subject: [PATCH 04/17] Update redirected internal links in search-github (#62121) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .../about-searching-on-github.md | 6 +++--- .../enabling-repository-search-across-environments.md | 2 +- .../sorting-search-results.md | 2 +- .../understanding-the-search-syntax.md | 2 +- .../searching-on-github/searching-github-marketplace.md | 2 +- 5 files changed, 7 insertions(+), 7 deletions(-) diff --git a/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md b/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md index 7a749e9247c9..34b12a620745 100644 --- a/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md +++ b/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md @@ -36,7 +36,7 @@ After typing a search query, you can press **Enter** to go to the full search re > [!NOTE] > * {% data reusables.search.required_login %} -> * {% data variables.product.prodname_pages %} sites are not searchable on {% data variables.product.github %}. However you can search the source content if it exists in the default branch of a repository, using code search. For more information, see [AUTOTITLE]{% ifversion code-search-upgrade %}(/search-github/github-code-search/understanding-github-code-search-syntax){% else %}(/search-github/searching-on-github/searching-code){% endif %}. For more information about {% data variables.product.prodname_pages %}, see [AUTOTITLE](/pages/getting-started-with-github-pages/about-github-pages) +> * {% data variables.product.prodname_pages %} sites are not searchable on {% data variables.product.github %}. However, you can search the source content if it exists in the default branch of a repository, using code search. For more information, see [AUTOTITLE]{% ifversion code-search-upgrade %}(/search-github/github-code-search/understanding-github-code-search-syntax){% else %}(/search-github/searching-on-github/searching-code){% endif %}. For more information about {% data variables.product.prodname_pages %}, see [AUTOTITLE](/pages/getting-started-with-github-pages/what-is-github-pages). > * Currently our search doesn't support exact matching.{% ifversion ghes %} > * Whenever you are searching in code files, only the first two results in each file will be returned.{% endif %} @@ -68,11 +68,11 @@ The {% data variables.search.advanced_url %} provides a visual interface for con ## Searching repositories on {% data variables.product.prodname_dotcom_the_website %} from your private enterprise environment -If you use {% data variables.product.prodname_dotcom_the_website %} or {% data variables.enterprise.data_residency_site %} as well as {% data variables.product.prodname_ghe_server %}, and an enterprise owner has enabled {% data variables.enterprise.prodname_unified_search %}, you can search across both environments at the same time from {% data variables.product.prodname_ghe_server %}. For more information, see {% ifversion fpt or ghec %}[AUTOTITLE](/enterprise-server@latest/search-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment) in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}[AUTOTITLE](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise). +If you use {% data variables.product.prodname_dotcom_the_website %} or {% data variables.enterprise.data_residency_site %} as well as {% data variables.product.prodname_ghe_server %}, and an enterprise owner has enabled {% data variables.enterprise.prodname_unified_search %}, you can search across both environments at the same time from {% data variables.product.prodname_ghe_server %}. For more information, see {% ifversion fpt or ghec %}[AUTOTITLE](/enterprise-server@latest/search-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment) in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}[AUTOTITLE](/admin/configuring-settings/configuring-github-connect/enabling-unified-search-for-your-enterprise). Your enterprise owner on {% data variables.product.prodname_ghe_server %} can separately enable {% data variables.enterprise.prodname_unified_search %} for all public repositories on {% data variables.product.prodname_dotcom_the_website %} and for private repositories owned by the organization or enterprise on {% data variables.product.prodname_dotcom_the_website %} or {% data variables.enterprise.data_residency_site %} that is connected to {% data variables.product.prodname_ghe_server %} through {% data variables.product.prodname_github_connect %}. -Before you can use {% data variables.enterprise.prodname_unified_search %} for private repositories, you must connect your user accounts across environments. For more information, see [AUTOTITLE](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment). +Before you can use {% data variables.enterprise.prodname_unified_search %} for private repositories, you must connect your user accounts across environments. For more information, see [AUTOTITLE](/search-github/getting-started-with-searching-on-github/enabling-repository-search-across-environments). When you search from {% data variables.product.prodname_ghe_server %}, only private repositories that you have access to and that are owned by the connected organization or enterprise account will be included in search results. Neither you nor anyone else will be able to search private repositories owned by your user account on {% data variables.product.prodname_dotcom_the_website %} or {% data variables.enterprise.data_residency_site %} from {% data variables.product.prodname_ghe_server %}. diff --git a/content/search-github/getting-started-with-searching-on-github/enabling-repository-search-across-environments.md b/content/search-github/getting-started-with-searching-on-github/enabling-repository-search-across-environments.md index 5bdade6a6ade..6fdd57068663 100644 --- a/content/search-github/getting-started-with-searching-on-github/enabling-repository-search-across-environments.md +++ b/content/search-github/getting-started-with-searching-on-github/enabling-repository-search-across-environments.md @@ -20,7 +20,7 @@ You can search for designated private repositories on {% data variables.product. ## Prerequisites -An enterprise owner for {% data variables.product.prodname_ghe_server %} must enable {% data variables.product.prodname_github_connect %} and {% data variables.enterprise.prodname_unified_search %} for private repositories. For more information, see [AUTOTITLE](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise). +An enterprise owner for {% data variables.product.prodname_ghe_server %} must enable {% data variables.product.prodname_github_connect %} and {% data variables.enterprise.prodname_unified_search %} for private repositories. For more information, see [AUTOTITLE](/admin/configuring-settings/configuring-github-connect/enabling-unified-search-for-your-enterprise). ## Enabling unified repository search from {% data variables.product.prodname_ghe_server %} diff --git a/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md b/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md index d702a5ca241a..78929cc348ed 100644 --- a/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md +++ b/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md @@ -114,4 +114,4 @@ The `sort:updated` qualifier sorts by how recently the items were updated. ## Further reading * [AUTOTITLE](/search-github/getting-started-with-searching-on-github/about-searching-on-github) -* [AUTOTITLE](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests) +* [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/filtering-and-searching-issues-and-pull-requests) diff --git a/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md b/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md index 71ab2dc073d5..65d800aa1c8d 100644 --- a/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md +++ b/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md @@ -104,7 +104,7 @@ If your search query contains a qualifier that requires a username, such as `use | `QUALIFIER:USERNAME` | [`author:nat`](https://github.com/search?q=author%3Anat&type=Commits) matches commits authored by @nat | | `QUALIFIER:@me` | [`is:issue assignee:@me`](https://github.com/search?q=is%3Aissue+assignee%3A%40me&type=Issues) matches issues assigned to the person viewing the results | | {% ifversion copilot %} | -| `QUALIFIER:@copilot` | [`is:pr reviewed-by:@copilot`](https://github.com/search?q=is:pr+reviewed-by:@copilot&type=pullrequests) matches pull requests reviewed by {% data variables.product.prodname_copilot_short %}. For more information, see [AUTOTITLE](/copilot/using-github-copilot/code-review/using-copilot-code-review). | +| `QUALIFIER:@copilot` | [`is:pr reviewed-by:@copilot`](https://github.com/search?q=is:pr+reviewed-by:@copilot&type=pullrequests) matches pull requests reviewed by {% data variables.product.prodname_copilot_short %}. For more information, see [AUTOTITLE](/copilot/how-tos/use-copilot-agents/request-a-code-review/use-code-review). | | {% endif %} | You can only use `@me` {% ifversion copilot %} or `@copilot` {% endif %} with a qualifier, and not as a search term, such as `@me main.workflow`. diff --git a/content/search-github/searching-on-github/searching-github-marketplace.md b/content/search-github/searching-on-github/searching-github-marketplace.md index a012d369f084..4f47fc206648 100644 --- a/content/search-github/searching-on-github/searching-github-marketplace.md +++ b/content/search-github/searching-on-github/searching-github-marketplace.md @@ -39,7 +39,7 @@ Anytime you search across all of {% data variables.product.prodname_dotcom %}, y {%- ifversion fpt %} * [AUTOTITLE](/search-github/searching-on-github/searching-github-models) {%- endif %} -* [AUTOTITLE](/actions/learn-github-actions/finding-and-customizing-actions) +* [AUTOTITLE](/actions/how-tos/write-workflows/choose-what-workflows-do/find-and-customize-actions) * [AUTOTITLE](/apps/using-github-apps/installing-a-github-app-from-github-marketplace-for-your-personal-account) * [AUTOTITLE](/apps/using-github-apps/installing-a-github-app-from-github-marketplace-for-your-organizations) * [AUTOTITLE](/apps/oauth-apps/using-oauth-apps/installing-an-oauth-app-in-your-personal-account) From 8781ba7a3b23ea8aefb7cecabf47ec5187cde61d Mon Sep 17 00:00:00 2001 From: Kevin Heis Date: Thu, 9 Jul 2026 06:41:23 -0700 Subject: [PATCH 05/17] Update redirected internal links in miscellaneous small content areas (#62166) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .../limiting-interactions-in-your-organization.md | 2 +- .../limiting-interactions-in-your-repository.md | 2 +- .../locking-conversations.md | 2 +- .../creating-a-default-community-health-file.md | 4 ++-- ...reating-a-pull-request-template-for-your-repository.md | 2 +- .../configuring-git-for-github-desktop.md | 8 ++++---- ...creating-your-first-repository-using-github-desktop.md | 2 +- ...eating-an-issue-or-pull-request-from-github-desktop.md | 2 +- .../collaborating-with-maintainers-using-discussions.md | 4 ++-- .../participating-in-a-discussion.md | 2 +- ...est-practices-for-community-conversations-on-github.md | 4 ++-- .../managing-discussions.md | 2 +- .../about-enterprise-billing.md | 2 +- .../about-migrating-to-github-enterprise-cloud.md | 2 +- .../choose-an-enterprise-type.md | 8 ++++---- .../using-the-support-portal.md | 4 ++-- .../github-cli/creating-github-cli-extensions.md | 2 +- content/github-cli/github-cli/github-cli-telemetry.md | 2 +- content/github-cli/github-cli/quickstart.md | 2 +- .../integrations/concepts/about-building-integrations.md | 8 ++++---- content/integrations/concepts/about-integrations.md | 6 +++--- content/integrations/how-tos/slack/use-github-in-slack.md | 2 +- 22 files changed, 37 insertions(+), 37 deletions(-) diff --git a/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md b/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md index ab5b6da7eb01..e755f51f69a3 100644 --- a/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md +++ b/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md @@ -42,6 +42,6 @@ Organization owners and moderators can also block users for a specific amount of * [AUTOTITLE](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) * [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/managing-an-individuals-access-to-an-organization-repository) -* [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository) +* [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/repository-access-and-collaboration/permission-levels-for-a-personal-account-repository) * [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization) * [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization) diff --git a/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md b/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md index f18d4cd231bb..fcbdb02fd0e8 100644 --- a/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md +++ b/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md @@ -56,6 +56,6 @@ To configure the pull request limit, navigate to the **Interaction limits** sett * [AUTOTITLE](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) * [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/managing-an-individuals-access-to-an-organization-repository) -* [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository) +* [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/repository-access-and-collaboration/permission-levels-for-a-personal-account-repository) * [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization) * [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization) diff --git a/content/communities/moderating-comments-and-conversations/locking-conversations.md b/content/communities/moderating-comments-and-conversations/locking-conversations.md index e644438cf514..2aa0cf7cf901 100644 --- a/content/communities/moderating-comments-and-conversations/locking-conversations.md +++ b/content/communities/moderating-comments-and-conversations/locking-conversations.md @@ -23,7 +23,7 @@ Locking a conversation creates a timeline event that is visible to anyone with r For anyone not meeting this criteria the locking actor will be anonymized. ![Screenshot of a timeline event, which says "octo-org locked as too heated and limited conversation to collaborators 2 minutes ago."](/assets/images/help/issues/anonymized-timeline-entry-for-locked-conversation.png) -While a conversation is locked, only [people with write access](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization) and [repository owners and collaborators](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository#collaborator-access-for-a-repository-owned-by-a-personal-account) can add, hide, and delete comments. Reactions and votes in a locked conversation are disabled for all users. +While a conversation is locked, only [people with write access](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization) and [repository owners and collaborators](/repositories/managing-your-repositorys-settings-and-features/repository-access-and-collaboration/permission-levels-for-a-personal-account-repository#collaborator-access-for-a-repository-owned-by-a-personal-account) can add, hide, and delete comments. Reactions and votes in a locked conversation are disabled for all users. To search for locked conversations in a repository that is not archived, you can use the search qualifiers `is:locked` and `archived:false`. Conversations are automatically locked in archived repositories. For more information, see [AUTOTITLE](/search-github/searching-on-github/searching-issues-and-pull-requests#search-based-on-whether-a-conversation-is-locked). diff --git a/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md b/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md index d19110b16c05..c3502f112a14 100644 --- a/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md +++ b/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md @@ -41,7 +41,7 @@ As a repository maintainer, you can use the community standards checklist to see ## About security policies {% ifversion fpt or ghec %} -After someone reports a security vulnerability in your project, you can use {% data variables.product.prodname_security_advisories %} to disclose, fix, and publish information about the vulnerability. For more information about the process of reporting and disclosing vulnerabilities in {% data variables.product.prodname_dotcom %}, see [AUTOTITLE](/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github). For more information about repository security advisories, see [AUTOTITLE](/code-security/security-advisories/working-with-repository-security-advisories/about-repository-security-advisories). +After someone reports a security vulnerability in your project, you can use {% data variables.product.prodname_security_advisories %} to disclose, fix, and publish information about the vulnerability. For more information about the process of reporting and disclosing vulnerabilities in {% data variables.product.prodname_dotcom %}, see [AUTOTITLE](/code-security/concepts/vulnerability-reporting-and-management/coordinated-disclosure#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github). For more information about repository security advisories, see [AUTOTITLE](/code-security/concepts/vulnerability-reporting-and-management/repository-security-advisories). {% endif %} {% ifversion ghes %} @@ -67,7 +67,7 @@ You can create defaults in your organization or personal account for the followi | {% endif %} | | _GOVERNANCE.md_ | A GOVERNANCE file lets people know about how your project is governed. For example, it might discuss project roles and how decisions are made. For more information, see [Leadership and Governance - Open Source Guides](https://opensource.guide/leadership-and-governance/#understanding-governance-for-your-growing-project). | | Issue and pull request templates and _config.yml_ | Issue and pull request templates customize and standardize the information you'd like contributors to include when they open issues and pull requests in your repository. For more information, see [AUTOTITLE](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates).

If an issue template sets a label, that label must be created in your `.github` repository and any repositories where the template will be used.{% ifversion ghec or ghes %} Organization-wide issue and pull request templates require the `.github` repository to be public.{% endif %} | -| _SECURITY.md_ | A SECURITY file gives instructions on how to report a security vulnerability in your project and description that hyperlinks the file. For more information, see [AUTOTITLE](/code-security/getting-started/adding-a-security-policy-to-your-repository). | +| _SECURITY.md_ | A SECURITY file gives instructions on how to report a security vulnerability in your project and description that hyperlinks the file. For more information, see [AUTOTITLE](/code-security/how-tos/report-and-fix-vulnerabilities/configure-vulnerability-reporting/add-security-policy). | | _SUPPORT.md_ | A SUPPORT file lets people know about ways to get help with your project. For more information, see [AUTOTITLE](/communities/setting-up-your-project-for-healthy-contributions/adding-support-resources-to-your-project). | You cannot create a default license file. License files must be added to individual repositories so the file will be included when a project is cloned, packaged, or downloaded. diff --git a/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md b/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md index 1d6357d78cf8..93529f761325 100644 --- a/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md +++ b/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md @@ -39,5 +39,5 @@ You can create default pull request templates for your organization or personal ## Further reading * [AUTOTITLE](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates) -* [AUTOTITLE](/issues/tracking-your-work-with-issues/creating-an-issue) +* [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/creating-an-issue) * [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request) diff --git a/content/desktop/configuring-and-customizing-github-desktop/configuring-git-for-github-desktop.md b/content/desktop/configuring-and-customizing-github-desktop/configuring-git-for-github-desktop.md index 3e151851d41d..86921ffaf01e 100644 --- a/content/desktop/configuring-and-customizing-github-desktop/configuring-git-for-github-desktop.md +++ b/content/desktop/configuring-and-customizing-github-desktop/configuring-git-for-github-desktop.md @@ -24,7 +24,7 @@ If the email address that has been set in your Git configuration does not match {% data variables.product.prodname_desktop %} also allows you to change the default branch name that you would like to use when creating new repositories. By default, {% data variables.product.prodname_desktop %} uses `main` as the default branch name in any new repositories you create. > [!TIP] -> Anyone will be able to see the email address in your Git configuration if you make public commits. For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address). +> Anyone will be able to see the email address in your Git configuration if you make public commits. For more information, see [AUTOTITLE](/account-and-profile/how-tos/email-preferences/setting-your-commit-email-address). ## Configuring your global author information @@ -149,7 +149,7 @@ For more information about Git hooks in {% data variables.product.prodname_deskt ## Further reading -* [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account) -* [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address) +* [AUTOTITLE](/account-and-profile/how-tos/email-preferences/adding-an-email-address-to-your-github-account) +* [AUTOTITLE](/account-and-profile/how-tos/email-preferences/setting-your-commit-email-address) * [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches) -* [AUTOTITLE](/get-started/getting-started-with-git) +* [AUTOTITLE](/get-started/git-basics) diff --git a/content/desktop/overview/creating-your-first-repository-using-github-desktop.md b/content/desktop/overview/creating-your-first-repository-using-github-desktop.md index bf38d50b7563..ef69619c0855 100644 --- a/content/desktop/overview/creating-your-first-repository-using-github-desktop.md +++ b/content/desktop/overview/creating-your-first-repository-using-github-desktop.md @@ -122,6 +122,6 @@ You've now created a repository, published the repository to {% data variables.p ## Further reading -* [AUTOTITLE](/get-started/getting-started-with-git) +* [AUTOTITLE](/get-started/git-basics) * [AUTOTITLE](/get-started/learning-about-github) * [AUTOTITLE](/get-started) diff --git a/content/desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request-from-github-desktop.md b/content/desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request-from-github-desktop.md index 422ad69437d7..fa6877b4e67d 100644 --- a/content/desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request-from-github-desktop.md +++ b/content/desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request-from-github-desktop.md @@ -18,7 +18,7 @@ category: --- ## About issues and pull requests -You can use issues to track ideas, bugs, tasks, and other information that's important to your project. You can create an issue in your project's repository with {% data variables.product.prodname_desktop %}. For more information about issues, see [AUTOTITLE](/issues/tracking-your-work-with-issues/about-issues). +You can use issues to track ideas, bugs, tasks, and other information that's important to your project. You can create an issue in your project's repository with {% data variables.product.prodname_desktop %}. For more information about issues, see [AUTOTITLE](/issues/tracking-your-work-with-issues/learning-about-issues/about-issues). After you create a branch and make changes to files in a project, you can create a pull request. With a pull request, you can propose, discuss, and iterate on changes before you merge the changes into the project. You can create a pull request in your project's repository with {% data variables.product.prodname_desktop %}. For more information about pull requests, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests). diff --git a/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md b/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md index 1324846cbac2..aafab30556d9 100644 --- a/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md +++ b/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md @@ -20,7 +20,7 @@ category: Repository administrators and project maintainers can delete a discussion in that repository. Similarly, administrators and maintainers of the source repository for an organization's discussions can delete a discussion in that organization. For more information, see [AUTOTITLE](/discussions/managing-discussions-for-your-community/managing-discussions#deleting-a-discussion). -{% data variables.product.prodname_dotcom %} will automatically recognize community members who contribute the most comments marked as answers to discussions with a question/answer format. {%- ifversion fpt %} These members appear in a list of the most helpful contributors to the project's discussions, if their privacy settings allow. For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private).{%- endif %}{%- ifversion ghes or ghec %} These members appear in a list of the most helpful contributors to the project's discussions.{%- endif %} +{% data variables.product.prodname_dotcom %} will automatically recognize community members who contribute the most comments marked as answers to discussions with a question/answer format. {%- ifversion fpt %} These members appear in a list of the most helpful contributors to the project's discussions, if their privacy settings allow. For more information, see [AUTOTITLE](/account-and-profile/how-tos/profile-customization/setting-your-profile-to-private).{%- endif %}{%- ifversion ghes or ghec %} These members appear in a list of the most helpful contributors to the project's discussions.{%- endif %} As your project grows, you can grant higher access permissions to active members of your community. For more information, see [AUTOTITLE](/discussions/guides/granting-higher-permissions-to-top-contributors). @@ -32,7 +32,7 @@ For more information about participation in discussions, see [AUTOTITLE](/discus {% ifversion copilot %} -> [!TIP] You can also use {% data variables.copilot.copilot_chat_short %} to generate ideas, outlines, or drafts for discussions, based on your pull requests and issues. See [AUTOTITLE](/copilot/copilot-chat-cookbook/documenting-code/writing-discussions-or-blog-posts). +> [!TIP] You can also use {% data variables.copilot.copilot_chat_short %} to generate ideas, outlines, or drafts for discussions, based on your pull requests and issues. See [AUTOTITLE](/copilot/tutorials/copilot-cookbook/document-code/write-discussions-or-blog-posts). {% endif %} diff --git a/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md index 94ab30bf4a58..233a65633957 100644 --- a/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md +++ b/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md @@ -27,7 +27,7 @@ In addition to starting or viewing discussions and polls, you can: {% ifversion copilot %} -> [!TIP] You can also use {% data variables.copilot.copilot_chat_short %} to generate ideas, outlines, or drafts for discussions based on your recent pull requests and issues. See [AUTOTITLE](/copilot/copilot-chat-cookbook/documenting-code/writing-discussions-or-blog-posts). +> [!TIP] You can also use {% data variables.copilot.copilot_chat_short %} to generate ideas, outlines, or drafts for discussions based on your recent pull requests and issues. See [AUTOTITLE](/copilot/tutorials/copilot-cookbook/document-code/write-discussions-or-blog-posts). {% endif %} diff --git a/content/discussions/guides/best-practices-for-community-conversations-on-github.md b/content/discussions/guides/best-practices-for-community-conversations-on-github.md index d946e889dc0c..93318642da8f 100644 --- a/content/discussions/guides/best-practices-for-community-conversations-on-github.md +++ b/content/discussions/guides/best-practices-for-community-conversations-on-github.md @@ -19,7 +19,7 @@ Since {% data variables.product.prodname_discussions %} is an open forum, there * Capturing a diverse experience and distilling it down to main points * Opening an issue to take action based on the conversation, where applicable -For more information about opening an issue and cross-referencing a discussion, see [AUTOTITLE](/issues/tracking-your-work-with-issues/creating-an-issue). +For more information about opening an issue and cross-referencing a discussion, see [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/creating-an-issue). ## Learning about conversations on GitHub @@ -33,7 +33,7 @@ You can use {% data variables.product.prodname_discussions %} to discuss big pic You might use repository discussions to discuss topics that are specific to the repository. If your project spans multiple repositories, you might use organization discussions to discuss topics that aren't specific to a single repository in your organization. -Issues are useful for discussing specific details of a project such as bug reports and planned improvements. For more information, see [AUTOTITLE](/issues/tracking-your-work-with-issues/about-issues). Pull requests allow you to comment directly on proposed changes. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) and [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request). +Issues are useful for discussing specific details of a project such as bug reports and planned improvements. For more information, see [AUTOTITLE](/issues/tracking-your-work-with-issues/learning-about-issues/about-issues). Pull requests allow you to comment directly on proposed changes. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) and [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request). ## Following contributing guidelines diff --git a/content/discussions/managing-discussions-for-your-community/managing-discussions.md b/content/discussions/managing-discussions-for-your-community/managing-discussions.md index 8291905e3fd7..e8bc83be2f01 100644 --- a/content/discussions/managing-discussions-for-your-community/managing-discussions.md +++ b/content/discussions/managing-discussions-for-your-community/managing-discussions.md @@ -22,7 +22,7 @@ Organization owners can choose the permissions required to create a discussion i As a discussions maintainer, you can create community resources to encourage discussions that are aligned with the overall project goal and maintain a friendly open forum for collaborators. Creating{% ifversion fpt or ghec %} a code of conduct or{% endif %} contribution guidelines for collaborators to follow will help facilitate a collaborative and productive forum. For more information on creating community resources, see{% ifversion fpt or ghec %} [AUTOTITLE](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project), and{% endif %} [AUTOTITLE](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors). -When a discussion yields an idea or bug that is ready to be worked on, you can create a new issue from a discussion. For more information, see [AUTOTITLE](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion). +When a discussion yields an idea or bug that is ready to be worked on, you can create a new issue from a discussion. For more information, see [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/creating-an-issue#creating-an-issue-from-a-discussion). You can pin a discussion to the top of the list of discussions for the repository or organization. You can also pin a discussion to a specific category. For more information, see [AUTOTITLE](/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion). diff --git a/content/enterprise-onboarding/getting-started-with-your-enterprise/about-enterprise-billing.md b/content/enterprise-onboarding/getting-started-with-your-enterprise/about-enterprise-billing.md index a839f0537b2a..0c146918aeaf 100644 --- a/content/enterprise-onboarding/getting-started-with-your-enterprise/about-enterprise-billing.md +++ b/content/enterprise-onboarding/getting-started-with-your-enterprise/about-enterprise-billing.md @@ -31,7 +31,7 @@ For prices and monthly allowances, see {% data variables.product.pricing_link %} ## Adding a payment method -To pay for licenses and services, you can use a credit card, PayPal, or a Microsoft Azure subscription. For instructions, see [AUTOTITLE](/billing/managing-your-billing/managing-your-payment-and-billing-information). +To pay for licenses and services, you can use a credit card, PayPal, or a Microsoft Azure subscription. For instructions, see [AUTOTITLE](/billing/how-tos/set-up-payment/manage-payment-info). ## Next steps diff --git a/content/enterprise-onboarding/getting-started-with-your-enterprise/about-migrating-to-github-enterprise-cloud.md b/content/enterprise-onboarding/getting-started-with-your-enterprise/about-migrating-to-github-enterprise-cloud.md index c93cc66e6bdb..b87edc6e7807 100644 --- a/content/enterprise-onboarding/getting-started-with-your-enterprise/about-migrating-to-github-enterprise-cloud.md +++ b/content/enterprise-onboarding/getting-started-with-your-enterprise/about-migrating-to-github-enterprise-cloud.md @@ -37,4 +37,4 @@ If you're planning to switch to {% data variables.product.prodname_actions %}, w ## Next steps -Now that you've started your trial and added users to your enterprise, you can set up organizations and teams to manage access. See [AUTOTITLE](/enterprise-onboarding/setting-up-organizations-and-teams/best-practices-for-organizations-in-your-enterprise). +Now that you've started your trial and added users to your enterprise, you can set up organizations and teams to manage access. See [AUTOTITLE](/enterprise-onboarding/setting-up-organizations-and-teams/best-practices). diff --git a/content/enterprise-onboarding/getting-started-with-your-enterprise/choose-an-enterprise-type.md b/content/enterprise-onboarding/getting-started-with-your-enterprise/choose-an-enterprise-type.md index 062d82b76f53..291cb3eee996 100644 --- a/content/enterprise-onboarding/getting-started-with-your-enterprise/choose-an-enterprise-type.md +++ b/content/enterprise-onboarding/getting-started-with-your-enterprise/choose-an-enterprise-type.md @@ -60,19 +60,19 @@ Consider whether you already use, or can adopt, a supported identity management If you cannot use a paved-path integration, you can use another identity management system that **meets our guidelines**. -For full details, see [AUTOTITLE](/enterprise-cloud@latest/admin/identity-and-access-management/understanding-iam-for-enterprises/about-enterprise-managed-users#identity-management-systems). +For full details, see [AUTOTITLE](/enterprise-cloud@latest/admin/concepts/identity-and-access-management/enterprise-managed-users#identity-management-systems). ### Personal accounts You can use any external identity management system that adheres to the **SAML 2.0** standard. -{% data variables.product.company_short %} officially supports and tests some systems. See [AUTOTITLE](/enterprise-cloud@latest/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise#supported-identity-providers). +{% data variables.product.company_short %} officially supports and tests some systems. See [AUTOTITLE](/enterprise-cloud@latest/admin/managing-iam/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise#supported-identity-providers). ## Do you need public repositories, gists, or {% data variables.product.prodname_pages %} sites? To prevent enterprise members from accidentally leaking corporate-owned content to the public, {% data variables.product.prodname_emus %} imposes **strong restrictions** on what users can do. * {% data variables.enterprise.prodname_managed_users_caps %} cannot create public repositories, gists of any visibility, or {% data variables.product.prodname_pages %} sites that are visible outside the enterprise. -* For a full list of restrictions, see [AUTOTITLE](/enterprise-cloud@latest/admin/identity-and-access-management/understanding-iam-for-enterprises/abilities-and-restrictions-of-managed-user-accounts). +* For a full list of restrictions, see [AUTOTITLE](/enterprise-cloud@latest/admin/managing-iam/understanding-iam-for-enterprises/abilities-and-restrictions-of-managed-user-accounts). Review the restrictions with your users, and confirm whether they will hinder your existing workflows. If so, an enterprise with personal accounts may be a better choice. @@ -80,7 +80,7 @@ Review the restrictions with your users, and confirm whether they will hinder yo {% data variables.enterprise.prodname_managed_users_caps %} can only contribute to repositories within your enterprise. If your developers must contribute to repositories outside of your enterprise (including private repositories), {% data variables.product.prodname_emus %} may not be right for you. -For a managed user to collaborate outside your enterprise, they must also maintain a separate, personal account. The complexity of regularly switching between accounts can increase the risk of mistakenly leaking internal code to the public. For details of the required workflow, see [AUTOTITLE](/enterprise-cloud@latest/admin/identity-and-access-management/understanding-iam-for-enterprises/getting-started-with-enterprise-managed-users#support-developers-with-multiple-user-accounts). +For a managed user to collaborate outside your enterprise, they must also maintain a separate, personal account. The complexity of regularly switching between accounts can increase the risk of mistakenly leaking internal code to the public. For details of the required workflow, see [AUTOTITLE](/enterprise-cloud@latest/admin/managing-iam/understanding-iam-for-enterprises/getting-started-with-enterprise-managed-users#support-developers-with-multiple-user-accounts). ## Can your enterprise tolerate migration costs? diff --git a/content/enterprise-onboarding/support-for-your-enterprise/using-the-support-portal.md b/content/enterprise-onboarding/support-for-your-enterprise/using-the-support-portal.md index 14598f3934db..61278e74cea0 100644 --- a/content/enterprise-onboarding/support-for-your-enterprise/using-the-support-portal.md +++ b/content/enterprise-onboarding/support-for-your-enterprise/using-the-support-portal.md @@ -21,8 +21,8 @@ The {% data variables.contact.enterprise_portal %} offers single sign-on (SSO) c Before you start creating tickets associated with your enterprise account on {% data variables.product.prodname_dotcom_the_website %}, we recommend completing the following steps. 1. Identify the user on {% data variables.product.prodname_dotcom_the_website %} who is an owner of your enterprise account. -1. Configure a verified domain. For more information, see [AUTOTITLE](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise). -1. Add owners, billing managers, or support-entitled members to your enterprise account. For more information, see [AUTOTITLE](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise) and [AUTOTITLE](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise). +1. Configure a verified domain. For more information, see [AUTOTITLE](/enterprise-cloud@latest/admin/configuring-settings/configuring-user-applications-for-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise). +1. Add owners, billing managers, or support-entitled members to your enterprise account. For more information, see [AUTOTITLE](/enterprise-cloud@latest/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise) and [AUTOTITLE](/enterprise-cloud@latest/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise). ## Next steps diff --git a/content/github-cli/github-cli/creating-github-cli-extensions.md b/content/github-cli/github-cli/creating-github-cli-extensions.md index d8766900ad34..edb8baaee9e6 100644 --- a/content/github-cli/github-cli/creating-github-cli-extensions.md +++ b/content/github-cli/github-cli/creating-github-cli-extensions.md @@ -247,7 +247,7 @@ For more information, see [`gh help formatting`](https://cli.github.com/manual/g GOOS=darwin GOARCH=amd64 go build -o gh-EXTENSION-NAME-darwin-amd64 gh release create v1.0.0 ./*amd64* -1. Optionally, to help other users discover your extension, add the repository topic `gh-extension`. This will make the extension appear on the [`gh-extension` topic page](https://github.com/topics/gh-extension). For more information about how to add a repository topic, see [Classifying your repository with topics](/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics). +1. Optionally, to help other users discover your extension, add the repository topic `gh-extension`. This will make the extension appear on the [`gh-extension` topic page](https://github.com/topics/gh-extension). For more information about how to add a repository topic, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics). ## Tips for writing precompiled {% data variables.product.prodname_cli %} extensions diff --git a/content/github-cli/github-cli/github-cli-telemetry.md b/content/github-cli/github-cli/github-cli-telemetry.md index 7ffe88b94e6f..1614eacce650 100644 --- a/content/github-cli/github-cli/github-cli-telemetry.md +++ b/content/github-cli/github-cli/github-cli-telemetry.md @@ -128,4 +128,4 @@ Telemetry events are sent to {% data variables.product.company_short %}'s intern {% data variables.product.prodname_cli %} allows you to add features to the product by installing {% data variables.product.company_short %}-authored and third-party extensions, including agents. These extensions may collect their own usage data and are not controlled by opting out. Consult the specific extension's documentation to learn about its telemetry reporting and whether it can be disabled. -This page describes client-side data collection for {% data variables.product.prodname_cli %} (`gh`). It does not apply to {% data variables.product.prodname_copilot %} or {% data variables.copilot.copilot_cli %}, which handle data collection separately. For information on the {% data variables.copilot.copilot_cli %}, see [AUTOTITLE](/free-pro-team@latest/copilot/concepts/agents/copilot-cli/about-copilot-cli) and [AUTOTITLE](/free-pro-team@latest/copilot/responsible-use/copilot-cli). +This page describes client-side data collection for {% data variables.product.prodname_cli %} (`gh`). It does not apply to {% data variables.product.prodname_copilot %} or {% data variables.copilot.copilot_cli %}, which handle data collection separately. For information on the {% data variables.copilot.copilot_cli %}, see [AUTOTITLE](/free-pro-team@latest/copilot/concepts/agents/copilot-cli/about-copilot-cli) and [AUTOTITLE](/free-pro-team@latest/copilot/responsible-use/agents). diff --git a/content/github-cli/github-cli/quickstart.md b/content/github-cli/github-cli/quickstart.md index 4cdf73c769d1..260d7295a377 100644 --- a/content/github-cli/github-cli/quickstart.md +++ b/content/github-cli/github-cli/quickstart.md @@ -47,7 +47,7 @@ Enter `gh repo create` and follow the on-screen instructions. You can create a n Enter `gh issue list --repo OWNER/REPO` to list the most recently created issues that are currently open for the specified repository. If you run the `issue` subcommand from within the directory of a local Git repository that has a remote on {% data variables.product.prodname_dotcom %} you can omit `--repo OWNER/REPO`. For example, enter `gh issue list --assignee "@me"` to list issues assigned to you in this repository, or `gh issue list --author monalisa` to list issues created by the user "monalisa." -You can also create a new issue, see [AUTOTITLE](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-with-github-cli), or search for an issue, see [AUTOTITLE](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests?tool=cli#searching-for-issues-and-pull-requests). +You can also create a new issue, see [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/creating-an-issue#creating-an-issue-with-github-cli), or search for an issue, see [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/filtering-and-searching-issues-and-pull-requests?tool=cli#searching-for-issues-and-pull-requests). ### Working with pull requests diff --git a/content/integrations/concepts/about-building-integrations.md b/content/integrations/concepts/about-building-integrations.md index 833706f0a8df..96308a29501f 100644 --- a/content/integrations/concepts/about-building-integrations.md +++ b/content/integrations/concepts/about-building-integrations.md @@ -18,8 +18,8 @@ Integrations are tools that extend {% data variables.product.company_short %}'s Many integrations are {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_actions %} workflows, or custom actions for {% data variables.product.prodname_actions %} workflows. * {% data variables.product.prodname_github_apps %} are integrations that run on the app owner's server or on a user device. For more information, see [AUTOTITLE](/apps/creating-github-apps/about-creating-github-apps/about-creating-github-apps). -* {% data variables.product.prodname_actions %} workflows are workflows that run when specific events occur on {% data variables.product.company_short %}. For more information, see [AUTOTITLE](/actions/learn-github-actions/understanding-github-actions). -* Custom actions are code that can be executed by a {% data variables.product.prodname_actions %} workflow. For more information, see [AUTOTITLE](/actions/creating-actions/about-custom-actions). +* {% data variables.product.prodname_actions %} workflows are workflows that run when specific events occur on {% data variables.product.company_short %}. For more information, see [AUTOTITLE](/actions/get-started/understand-github-actions). +* Custom actions are code that can be executed by a {% data variables.product.prodname_actions %} workflow. For more information, see [AUTOTITLE](/actions/concepts/workflows-and-actions/custom-actions). Your integration can use {% data variables.product.company_short %}'s API to fetch data and make changes to data on {% data variables.product.company_short %}. {% data variables.product.company_short %} has a REST API and a GraphQL API. For more information, see: @@ -29,8 +29,8 @@ Your integration can use {% data variables.product.company_short %}'s API to fet Your integration can use webhooks to learn when specific events happen on {% data variables.product.company_short %}. For more information, see [AUTOTITLE](/webhooks/about-webhooks). -{% ifversion fpt or ghec %} If your integration is a {% data variables.product.prodname_github_app %} or custom action, you can publish your integration on {% data variables.product.prodname_marketplace %}. For more information, see [AUTOTITLE](/apps/github-marketplace/github-marketplace-overview/about-github-marketplace-for-apps) and [AUTOTITLE](/actions/creating-actions/publishing-actions-in-github-marketplace).{% endif %} +{% ifversion fpt or ghec %} If your integration is a {% data variables.product.prodname_github_app %} or custom action, you can publish your integration on {% data variables.product.prodname_marketplace %}. For more information, see [AUTOTITLE](/apps/github-marketplace/github-marketplace-overview/about-github-marketplace-for-apps) and [AUTOTITLE](/actions/how-tos/create-and-publish-actions/publish-in-github-marketplace).{% endif %} {% ifversion fpt or ghec %} -If your integration uses generative AI, you can find and experiment with AI models for free on {% data variables.product.company_short %}. See [AUTOTITLE](/github-models/prototyping-with-ai-models). +If your integration uses generative AI, you can find and experiment with AI models for free on {% data variables.product.company_short %}. See [AUTOTITLE](/github-models/use-github-models/prototyping-with-ai-models). {% endif %} diff --git a/content/integrations/concepts/about-integrations.md b/content/integrations/concepts/about-integrations.md index f58ac7ede315..8f09a2bfe8a5 100644 --- a/content/integrations/concepts/about-integrations.md +++ b/content/integrations/concepts/about-integrations.md @@ -28,7 +28,7 @@ For a list of featured {% data variables.product.company_short %} integrations, If you want your {% data variables.product.prodname_ghe_server %} instance to use a third-party {% data variables.product.prodname_github_app %}, you can contact the app developer about making the {% data variables.product.prodname_github_app %} available for {% data variables.product.prodname_ghe_server %}. For more information, see [AUTOTITLE](/apps/sharing-github-apps/making-your-github-app-available-for-github-enterprise-server). -If you want your {% data variables.product.prodname_ghe_server %} instance to use third-party custom actions, you need to enable {% data variables.product.prodname_github_connect %}. For more information, see [AUTOTITLE](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect). +If you want your {% data variables.product.prodname_ghe_server %} instance to use third-party custom actions, you need to enable {% data variables.product.prodname_github_connect %}. For more information, see [AUTOTITLE](/admin/managing-github-actions-for-your-enterprise/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect). {% endif %} @@ -36,6 +36,6 @@ For more information about using integrations, see: * [AUTOTITLE](/apps/using-github-apps/about-using-github-apps) * [AUTOTITLE](/apps/oauth-apps/using-oauth-apps) -* [AUTOTITLE](/actions/learn-github-actions/finding-and-customizing-actions) +* [AUTOTITLE](/actions/how-tos/write-workflows/choose-what-workflows-do/find-and-customize-actions) -You can also build your own integrations. For more information, see [AUTOTITLE](/get-started/exploring-integrations/about-building-integrations). +You can also build your own integrations. For more information, see [AUTOTITLE](/integrations/concepts/about-building-integrations). diff --git a/content/integrations/how-tos/slack/use-github-in-slack.md b/content/integrations/how-tos/slack/use-github-in-slack.md index b7f9e1593dce..cd32429c097c 100644 --- a/content/integrations/how-tos/slack/use-github-in-slack.md +++ b/content/integrations/how-tos/slack/use-github-in-slack.md @@ -115,7 +115,7 @@ You can schedule reminders for pull request reviews in Slack. Reminders can be s You can configure scheduled reminders for yourself, your team, or your entire organization. For more information, see: -* [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders) +* [AUTOTITLE](/subscriptions-and-notifications/how-tos/managing-your-scheduled-reminders) * [AUTOTITLE](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team) * [AUTOTITLE](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization) From f6563f9663db132ef0f3fe55519a6d7608b67d30 Mon Sep 17 00:00:00 2001 From: Kevin Heis Date: Thu, 9 Jul 2026 06:41:31 -0700 Subject: [PATCH 06/17] Update redirected internal links in copilot (how-tos (part 1)) (#62161) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .../disable-for-organizations.md | 4 +- .../manage-access/grant-access.md | 2 +- .../configure-enterprise-managed-settings.md | 2 +- .../create-github-private-repo.md | 2 +- .../prepare-for-custom-agents.md | 4 +- .../manage-enterprise-policies.md | 2 +- .../manage-plan/subscribe.md | 6 +- .../manage-plan/upgrade-plan.md | 4 +- .../manage-for-enterprise/manage-spark.md | 4 +- .../add-copilot-cloud-agent.md | 6 +- .../configure-runner-for-coding-agent.md | 4 +- .../manage-access/grant-access.md | 8 +- .../manage-access/revoke-access.md | 6 +- .../manage-plan/cancel.md | 2 +- .../prepare-for-custom-agents.md | 2 +- .../review-user-activity-data.md | 8 +- .../view-code-generation.md | 2 +- .../view-usage-and-adoption.md | 4 +- .../how-tos/chat-with-copilot/chat-in-ide.md | 90 +++++++++---------- .../chat-in-windows-terminal.md | 6 +- .../get-started-with-chat-in-your-ide.md | 4 +- .../exclude-content-from-copilot.md | 6 +- .../review-changes.md | 2 +- ...add-repository-instructions-in-your-ide.md | 8 +- .../authenticate-to-ghecom.md | 2 +- .../configure-in-ide.md | 18 ++-- .../configure-network-settings.md | 16 ++-- .../how-tos/copilot-cli/cli-best-practices.md | 6 +- .../copilot-cli/cli-getting-started.md | 4 +- .../add-custom-instructions.md | 2 +- .../customize-copilot/add-mcp-servers.md | 10 +-- .../customize-copilot/plugins-creating.md | 4 +- .../customize-copilot/plugins-marketplace.md | 4 +- .../customize-copilot/use-hooks.md | 4 +- .../set-up-copilot-cli/add-lsp-servers.md | 2 +- .../configure-copilot-cli.md | 4 +- .../set-up-copilot-cli/install-copilot-cli.md | 6 +- .../use-copilot-cli/agentic-code-review.md | 4 +- .../use-copilot-cli/invoke-custom-agents.md | 4 +- .../use-copilot-cli/manage-pull-requests.md | 4 +- 40 files changed, 141 insertions(+), 141 deletions(-) diff --git a/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-access/disable-for-organizations.md b/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-access/disable-for-organizations.md index d3727cfe6a90..668386f1ce46 100644 --- a/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-access/disable-for-organizations.md +++ b/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-access/disable-for-organizations.md @@ -37,5 +37,5 @@ Once {% data variables.product.prodname_copilot_short %} is disabled, licenses t ## Further reading -* [AUTOTITLE](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot) -* [AUTOTITLE](/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-policies-and-features-for-copilot-in-your-enterprise) +* [AUTOTITLE](/billing/concepts/product-billing/github-copilot-licenses) +* [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-enterprise-policies) diff --git a/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-access/grant-access.md b/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-access/grant-access.md index b6bce54b19f9..299da1e65615 100644 --- a/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-access/grant-access.md +++ b/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-access/grant-access.md @@ -62,4 +62,4 @@ If your enterprise has a {% data variables.copilot.copilot_enterprise_short %} p * If your enterprise has a {% data variables.copilot.copilot_business_short %} plan, click **Enabled**. * If your enterprise has a {% data variables.copilot.copilot_enterprise_short %} plan, click either **Copilot: Enterprise** or **Copilot: Business** to assign a specific Copilot plan to the organization. -After you've enabled {% data variables.product.prodname_copilot_short %} for an organization in your enterprise, owners of the organization can grant access to some or all members of the organization. See [AUTOTITLE](/copilot/managing-github-copilot-in-your-organization/managing-access-for-copilot-business-in-your-organization). +After you've enabled {% data variables.product.prodname_copilot_short %} for an organization in your enterprise, owners of the organization can grant access to some or all members of the organization. See [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-organization/manage-access/grant-access). diff --git a/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/configure-enterprise-managed-settings.md b/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/configure-enterprise-managed-settings.md index f5d9bbfce10b..62d4329b0c3f 100644 --- a/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/configure-enterprise-managed-settings.md +++ b/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/configure-enterprise-managed-settings.md @@ -124,7 +124,7 @@ You can apply settings to control users' available plugin marketplaces and defau ## Setting {% data variables.product.prodname_copilot_short %} auto model selection as the default -You can set auto model selection as the default model for new conversations in {% data variables.copilot.copilot_cli_short %} and {% data variables.product.prodname_vscode_shortname %}. To learn more see [AUTOTITLE](/copilot/concepts/auto-model-selection). By setting it as the default for your enterprise, you ensure new conversations start with Auto model selected. +You can set auto model selection as the default model for new conversations in {% data variables.copilot.copilot_cli_short %} and {% data variables.product.prodname_vscode_shortname %}. To learn more see [AUTOTITLE](/copilot/concepts/models/auto-model-selection). By setting it as the default for your enterprise, you ensure new conversations start with Auto model selected. ### What setting Auto model as the default does diff --git a/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/create-github-private-repo.md b/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/create-github-private-repo.md index 6987204e6259..2de2c67d9076 100644 --- a/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/create-github-private-repo.md +++ b/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/create-github-private-repo.md @@ -40,4 +40,4 @@ The "Configuration summary" on the settings page will display the settings taken ## Next steps * [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/prepare-for-custom-agents) -* [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/configure-enterprise-plugin-standards) \ No newline at end of file +* [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/configure-enterprise-managed-settings) diff --git a/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/prepare-for-custom-agents.md b/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/prepare-for-custom-agents.md index 9e02573b0181..dad8d7ce7148 100644 --- a/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/prepare-for-custom-agents.md +++ b/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/prepare-for-custom-agents.md @@ -27,6 +27,6 @@ Before you can create and use {% data variables.copilot.custom_agents_short %}, ## Next steps -To reduce your administrative burden and empower your SMEs, you can delegate the creation and management of {% data variables.copilot.custom_agents_short %} in your enterprise by creating a team of AI managers. See [AUTOTITLE](/copilot/tutorials/roll-out-at-scale/establish-ai-managers). +To reduce your administrative burden and empower your SMEs, you can delegate the creation and management of {% data variables.copilot.custom_agents_short %} in your enterprise by creating a team of AI managers. See [AUTOTITLE](/copilot/tutorials/roll-out-at-scale/govern-at-scale/establish-ai-managers). -If you prefer to maintain full control over your enterprise's tooling to ensure security and compliance, you can create and manage {% data variables.copilot.custom_agents_short %} yourself. See [AUTOTITLE](/copilot/how-tos/use-copilot-agents/cloud-agent/test-custom-agents). +If you prefer to maintain full control over your enterprise's tooling to ensure security and compliance, you can create and manage {% data variables.copilot.custom_agents_short %} yourself. See [AUTOTITLE](/copilot/how-tos/copilot-on-github/customize-copilot/customize-cloud-agent/test-custom-agents). diff --git a/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-enterprise-policies.md b/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-enterprise-policies.md index 5ce70d5bef84..8610bb3060cc 100644 --- a/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-enterprise-policies.md +++ b/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-enterprise-policies.md @@ -19,7 +19,7 @@ category: When an organization owner assigns a {% data variables.product.prodname_copilot_short %} license to a member of their organization, the availability of features and models is controlled by policies. -If you're setting up {% data variables.product.prodname_copilot_short %} for the first time, see [AUTOTITLE](/copilot/tutorials/roll-out-at-scale/govern-for-adoption) for guidance on setting a governance posture that balances compliance with developer productivity. +If you're setting up {% data variables.product.prodname_copilot_short %} for the first time, see [AUTOTITLE](/copilot/tutorials/roll-out-at-scale/govern-at-scale/govern-for-adoption) for guidance on setting a governance posture that balances compliance with developer productivity. ## Defining policies for your enterprise diff --git a/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-plan/subscribe.md b/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-plan/subscribe.md index 28ad24caa31c..4884b7edde37 100644 --- a/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-plan/subscribe.md +++ b/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-plan/subscribe.md @@ -30,9 +30,9 @@ category: ## Next steps -* To finish setting up {% data variables.product.prodname_copilot_short %} for your enterprise, see [AUTOTITLE](/copilot/setting-up-github-copilot/setting-up-github-copilot-for-your-enterprise). -* For billing information, see [AUTOTITLE](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot#about-billing-for-github-copilot-business-and-github-copilot-enterprise) and [AUTOTITLE](/billing/managing-your-billing). +* To finish setting up {% data variables.product.prodname_copilot_short %} for your enterprise, see [AUTOTITLE](/copilot/how-tos/copilot-on-github/set-up-copilot/enable-copilot/set-up-for-enterprise). +* For billing information, see [AUTOTITLE](/billing/concepts/product-billing/github-copilot-licenses#about-billing-for-github-copilot-business-and-github-copilot-enterprise) and [AUTOTITLE](/billing/get-started). ## Further reading -* [AUTOTITLE](/copilot/about-github-copilot/subscription-plans-for-github-copilot) +* [AUTOTITLE](/copilot/get-started/plans) diff --git a/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-plan/upgrade-plan.md b/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-plan/upgrade-plan.md index cfff964f53bb..509e423c8294 100644 --- a/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-plan/upgrade-plan.md +++ b/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-plan/upgrade-plan.md @@ -29,7 +29,7 @@ category: ## Next steps -After upgrading to {% data variables.copilot.copilot_enterprise_short %}, you can assign {% data variables.copilot.copilot_enterprise_short %} or {% data variables.copilot.copilot_business_short %} to individual organizations in the enterprise. See [AUTOTITLE](/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-access-to-copilot-in-your-enterprise/enabling-copilot-for-organizations-in-your-enterprise). +After upgrading to {% data variables.copilot.copilot_enterprise_short %}, you can assign {% data variables.copilot.copilot_enterprise_short %} or {% data variables.copilot.copilot_business_short %} to individual organizations in the enterprise. See [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-access/grant-access). ## Troubleshooting plan migrations @@ -48,4 +48,4 @@ Some migrations cannot be completed through self-service options. ## Further reading -* [AUTOTITLE](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot) +* [AUTOTITLE](/billing/concepts/product-billing/github-copilot-licenses) diff --git a/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-spark.md b/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-spark.md index 4f112a1a3777..5b21ef68606b 100644 --- a/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-spark.md +++ b/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-spark.md @@ -30,7 +30,7 @@ To use {% data variables.product.prodname_spark_short %}, your enterprise must b By default, {% data variables.product.prodname_spark_short %} is **disabled** for users who receive a {% data variables.copilot.copilot_enterprise_short %} license from an enterprise-owned organization. -You can allow members to use {% data variables.product.prodname_spark_short %} from the AI Controls tab for your enterprise. See [AUTOTITLE](/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-policies-and-features-for-copilot-in-your-enterprise#defining-policies-for-your-enterprise). +You can allow members to use {% data variables.product.prodname_spark_short %} from the AI Controls tab for your enterprise. See [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-enterprise-policies#defining-policies-for-your-enterprise). {% data reusables.enterprise-accounts.policy-enablement-next-steps %} @@ -44,4 +44,4 @@ Was this article helpful in enabling and managing {% data variables.product.prod ## Further reading -* [AUTOTITLE](/copilot/responsible-use-of-github-copilot-features/responsible-use-of-github-spark) +* [AUTOTITLE](/copilot/responsible-use/agents) diff --git a/content/copilot/how-tos/administer-copilot/manage-for-organization/add-copilot-cloud-agent.md b/content/copilot/how-tos/administer-copilot/manage-for-organization/add-copilot-cloud-agent.md index 493d48c9053d..393b14f6df25 100644 --- a/content/copilot/how-tos/administer-copilot/manage-for-organization/add-copilot-cloud-agent.md +++ b/content/copilot/how-tos/administer-copilot/manage-for-organization/add-copilot-cloud-agent.md @@ -28,7 +28,7 @@ category: {% data variables.copilot.copilot_cloud_agent %} and use of third-party MCP servers are disabled by default for organization members assigned a {% data variables.copilot.copilot_enterprise %} or {% data variables.copilot.copilot_business_short %} license by your organization. -Organizations with {% data variables.copilot.copilot_enterprise_short %} or {% data variables.copilot.copilot_business_short %} can enable these features for members on the {% data variables.product.prodname_copilot_short %} policies page for their organization. See [Enabling {% data variables.product.prodname_copilot_short %} features in your organization](/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-policies-for-copilot-in-your-organization#enabling-copilot-features-in-your-organization). +Organizations with {% data variables.copilot.copilot_enterprise_short %} or {% data variables.copilot.copilot_business_short %} can enable these features for members on the {% data variables.product.prodname_copilot_short %} policies page for their organization. See [Enabling {% data variables.product.prodname_copilot_short %} features in your organization](/copilot/how-tos/administer-copilot/manage-for-organization/manage-policies#enabling-copilot-features-in-your-organization). * For the "{% data variables.copilot.copilot_cloud_agent %}" policy, select "Enabled". * For the "MCP servers on {% data variables.product.prodname_dotcom_the_website %}" policy, select "Enabled". @@ -58,7 +58,7 @@ Once {% data variables.copilot.copilot_cloud_agent %} is enabled for a repositor ## Managing the agent firewall for your organization -Organization owners can configure the {% data variables.copilot.copilot_cloud_agent %} firewall for their organization, including whether it is enabled for the organization and which external hosts and URLs the agent can access. For more information, see [AUTOTITLE](/copilot/how-tos/use-copilot-agents/cloud-agent/customize-the-agent-firewall). +Organization owners can configure the {% data variables.copilot.copilot_cloud_agent %} firewall for their organization, including whether it is enabled for the organization and which external hosts and URLs the agent can access. For more information, see [AUTOTITLE](/copilot/how-tos/copilot-on-github/customize-copilot/customize-cloud-agent/customize-the-agent-firewall). ## Next steps @@ -67,5 +67,5 @@ Organization owners can configure the {% data variables.copilot.copilot_cloud_ag * Encourage members to educate themselves about setting up their repository to get the most from {% data variables.copilot.copilot_cloud_agent %}. Useful resources: * [AUTOTITLE](/copilot/tutorials/cloud-agent/get-the-best-results) - * [AUTOTITLE](/copilot/how-tos/use-copilot-agents/cloud-agent/customize-the-agent-environment) + * [AUTOTITLE](/copilot/how-tos/copilot-on-github/customize-copilot/customize-cloud-agent/customize-the-agent-environment) * [AUTOTITLE](/copilot/concepts/agents/cloud-agent/risks-and-mitigations) diff --git a/content/copilot/how-tos/administer-copilot/manage-for-organization/configure-runner-for-coding-agent.md b/content/copilot/how-tos/administer-copilot/manage-for-organization/configure-runner-for-coding-agent.md index 373c54e00e6d..e65acc1d39df 100644 --- a/content/copilot/how-tos/administer-copilot/manage-for-organization/configure-runner-for-coding-agent.md +++ b/content/copilot/how-tos/administer-copilot/manage-for-organization/configure-runner-for-coding-agent.md @@ -42,11 +42,11 @@ By default, repositories can override the organization-level runner configuratio {% data reusables.profile.org_settings %} {% data reusables.copilot.cloud-agent-settings %} 1. Under "Allow repositories to customize the runner type," toggle the setting to enable or disable repository-level customization. - * When enabled, repositories can override the default runner by setting the `runs-on` field in the `copilot-setup-steps` job of `copilot-setup-steps.yml`. See [AUTOTITLE](/copilot/how-tos/use-copilot-agents/cloud-agent/customize-the-agent-environment#configure-the-runner). + * When enabled, repositories can override the default runner by setting the `runs-on` field in the `copilot-setup-steps` job of `copilot-setup-steps.yml`. See [AUTOTITLE](/copilot/how-tos/copilot-on-github/customize-copilot/customize-cloud-agent/customize-the-agent-environment#configure-the-runner). * When disabled, all repositories in your organization will use the organization-level runner type. 1. Click **Save**. ## Further reading -* [AUTOTITLE](/copilot/how-tos/use-copilot-agents/cloud-agent/customize-the-agent-environment) +* [AUTOTITLE](/copilot/how-tos/copilot-on-github/customize-copilot/customize-cloud-agent/customize-the-agent-environment) * [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-organization/add-copilot-cloud-agent) diff --git a/content/copilot/how-tos/administer-copilot/manage-for-organization/manage-access/grant-access.md b/content/copilot/how-tos/administer-copilot/manage-for-organization/manage-access/grant-access.md index 905954b84fe7..a43f52117141 100644 --- a/content/copilot/how-tos/administer-copilot/manage-for-organization/manage-access/grant-access.md +++ b/content/copilot/how-tos/administer-copilot/manage-for-organization/manage-access/grant-access.md @@ -26,7 +26,7 @@ category: {% ifversion ghec %}After a {% data variables.product.prodname_dotcom %} enterprise owner enables {% data variables.copilot.copilot_enterprise_short %} or {% data variables.copilot.copilot_business_short %} for an organization, an owner of that organization can grant {% data variables.product.prodname_copilot %} access to members of their organization.{% else %}After setting up a {% data variables.copilot.copilot_business_short %} plan, an organization owner can grant {% data variables.product.prodname_copilot %} access to members of their organization.{% endif %} -Billing for {% data variables.product.prodname_copilot %} starts when you grant an organization member access, irrespective of when they first use {% data variables.product.prodname_copilot_short %}. If you grant an organization member access midway through a billing cycle, the cost is prorated for the remainder of the cycle. For more information, see [AUTOTITLE](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot). +Billing for {% data variables.product.prodname_copilot %} starts when you grant an organization member access, irrespective of when they first use {% data variables.product.prodname_copilot_short %}. If you grant an organization member access midway through a billing cycle, the cost is prorated for the remainder of the cycle. For more information, see [AUTOTITLE](/billing/concepts/product-billing/github-copilot-licenses). ## Granting access to {% data variables.product.prodname_copilot %} for all current and future users in your organization @@ -79,6 +79,6 @@ You can use {% data variables.product.prodname_dotcom %}'s REST API to grant acc ## Further reading * [{% data variables.product.prodname_copilot %} Trust Center](https://copilot.github.trust.page) -* [AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-github-copilot-features-in-your-organization/managing-policies-for-copilot-in-your-organization) -* [AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/reviewing-github-copilot-activity-in-your-organization/reviewing-usage-data-for-github-copilot-in-your-organization) -* [AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-access-to-github-copilot-in-your-organization/revoking-access-to-copilot-for-members-of-your-organization) +* [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-organization/manage-policies) +* [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-organization/review-activity/review-user-activity-data) +* [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-organization/manage-access/revoke-access) diff --git a/content/copilot/how-tos/administer-copilot/manage-for-organization/manage-access/revoke-access.md b/content/copilot/how-tos/administer-copilot/manage-for-organization/manage-access/revoke-access.md index b2fc717f2caf..9bbfb0e12ef9 100644 --- a/content/copilot/how-tos/administer-copilot/manage-for-organization/manage-access/revoke-access.md +++ b/content/copilot/how-tos/administer-copilot/manage-for-organization/manage-access/revoke-access.md @@ -24,7 +24,7 @@ Revoking access at the organization level only removes access for people who rec To remove access for those users, an enterprise owner must remove them from the enterprise team or unassign their license in the enterprise settings, which revokes access immediately. For more information, see [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-access/grant-access#assigning-licenses-to-users-or-teams). -For people whose access is revoked through organization-level revocation, the removal takes effect from the start of the next billing cycle. If you remove a seat during a cycle, the user will have access to {% data variables.product.prodname_copilot_short %} for the remainder of the billing cycle. For more information, see [AUTOTITLE](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot). +For people whose access is revoked through organization-level revocation, the removal takes effect from the start of the next billing cycle. If you remove a seat during a cycle, the user will have access to {% data variables.product.prodname_copilot_short %} for the remainder of the billing cycle. For more information, see [AUTOTITLE](/billing/concepts/product-billing/github-copilot-licenses). ## Revoking access to {% data variables.product.prodname_copilot_short %} for your whole organization @@ -55,5 +55,5 @@ You can use {% data variables.product.prodname_dotcom %}'s REST API to revoke ac ## Further reading * [{% data variables.product.prodname_copilot %} Trust Center](https://copilot.github.trust.page) -* [AUTOTITLE](/copilot/managing-github-copilot-in-your-organization/granting-access-to-copilot-for-members-of-your-organization). -* [AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/reviewing-github-copilot-activity-in-your-organization/reviewing-usage-data-for-github-copilot-in-your-organization) +* [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-organization/manage-access/grant-access). +* [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-organization/review-activity/review-user-activity-data) diff --git a/content/copilot/how-tos/administer-copilot/manage-for-organization/manage-plan/cancel.md b/content/copilot/how-tos/administer-copilot/manage-for-organization/manage-plan/cancel.md index 985db599203c..60411de7319a 100644 --- a/content/copilot/how-tos/administer-copilot/manage-for-organization/manage-plan/cancel.md +++ b/content/copilot/how-tos/administer-copilot/manage-for-organization/manage-plan/cancel.md @@ -21,7 +21,7 @@ category: {% ifversion ghec %} >[!NOTE] -> If your organization was granted access to {% data variables.product.prodname_copilot_short %} through an enterprise, your enterprise admin will need to cancel the plan instead. See [AUTOTITLE](/copilot/managing-copilot/managing-copilot-for-your-enterprise/canceling-copilot-for-your-enterprise). +> If your organization was granted access to {% data variables.product.prodname_copilot_short %} through an enterprise, your enterprise admin will need to cancel the plan instead. See [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-plan/cancel-plan). {% endif %} To cancel your {% data variables.copilot.copilot_business_short %} plan for your organization account, you need to remove all assigned {% data variables.product.prodname_copilot %} seats. diff --git a/content/copilot/how-tos/administer-copilot/manage-for-organization/prepare-for-custom-agents.md b/content/copilot/how-tos/administer-copilot/manage-for-organization/prepare-for-custom-agents.md index 485468a13e5f..7a1e831bed7d 100644 --- a/content/copilot/how-tos/administer-copilot/manage-for-organization/prepare-for-custom-agents.md +++ b/content/copilot/how-tos/administer-copilot/manage-for-organization/prepare-for-custom-agents.md @@ -40,4 +40,4 @@ If you don't already have a suitable repository, follow the steps below to creat ## Next steps -To trial {% data variables.copilot.custom_agents_short %}, see [AUTOTITLE](/copilot/how-tos/use-copilot-agents/cloud-agent/test-custom-agents). +To trial {% data variables.copilot.custom_agents_short %}, see [AUTOTITLE](/copilot/how-tos/copilot-on-github/customize-copilot/customize-cloud-agent/test-custom-agents). diff --git a/content/copilot/how-tos/administer-copilot/manage-for-organization/review-activity/review-user-activity-data.md b/content/copilot/how-tos/administer-copilot/manage-for-organization/review-activity/review-user-activity-data.md index 40b6b348fd0a..f35dac9ecc69 100644 --- a/content/copilot/how-tos/administer-copilot/manage-for-organization/review-activity/review-user-activity-data.md +++ b/content/copilot/how-tos/administer-copilot/manage-for-organization/review-activity/review-user-activity-data.md @@ -50,8 +50,8 @@ For more information about this property and other data in the activity report, ## Further reading {% ifversion ghec %} -* [AUTOTITLE](/copilot/managing-copilot/managing-copilot-for-your-enterprise/viewing-copilot-usage-for-your-enterprise){% endif %} +* [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-access/view-license-usage){% endif %} * [{% data variables.product.prodname_copilot %} Trust Center](https://copilot.github.trust.page) -* [AUTOTITLE](/copilot/managing-github-copilot-in-your-organization/granting-access-to-copilot-for-members-of-your-organization) -* [AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-access-to-github-copilot-in-your-organization/revoking-access-to-copilot-for-members-of-your-organization) -* [AUTOTITLE](/copilot/managing-copilot/configuring-and-auditing-content-exclusion/reviewing-changes-to-content-exclusions-for-github-copilot) +* [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-organization/manage-access/grant-access) +* [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-organization/manage-access/revoke-access) +* [AUTOTITLE](/copilot/how-tos/configure-content-exclusion/review-changes) diff --git a/content/copilot/how-tos/administer-copilot/view-code-generation.md b/content/copilot/how-tos/administer-copilot/view-code-generation.md index cdcc5789c270..09e727029d42 100644 --- a/content/copilot/how-tos/administer-copilot/view-code-generation.md +++ b/content/copilot/how-tos/administer-copilot/view-code-generation.md @@ -37,4 +37,4 @@ For a detailed list of available metrics and definitions, see [AUTOTITLE](/copil ## Next steps -To learn how to interpret the data in each chart and act on usage trends, see [AUTOTITLE](/copilot/reference/interpret-copilot-metrics). +To learn how to interpret the data in each chart and act on usage trends, see [AUTOTITLE](/copilot/reference/copilot-usage-metrics/interpret-copilot-metrics). diff --git a/content/copilot/how-tos/administer-copilot/view-usage-and-adoption.md b/content/copilot/how-tos/administer-copilot/view-usage-and-adoption.md index 4d524f8636ad..3e548c4d2d0f 100644 --- a/content/copilot/how-tos/administer-copilot/view-usage-and-adoption.md +++ b/content/copilot/how-tos/administer-copilot/view-usage-and-adoption.md @@ -26,7 +26,7 @@ After your initial rollout, the {% data variables.product.prodname_copilot_short {% data reusables.copilot.access-copilot-metrics-dashboard %} 1. In the left sidebar, click **{% data variables.product.prodname_copilot_short %} usage**. -Data in the dashboard is primarily based on IDE telemetry and is supplemented by server-side telemetry to capture additional active users. Data may appear up to three full UTC days behind the current date. See [AUTOTITLE](/copilot/concepts/copilot-metrics). +Data in the dashboard is primarily based on IDE telemetry and is supplemented by server-side telemetry to capture additional active users. Data may appear up to three full UTC days behind the current date. See [AUTOTITLE](/copilot/concepts/copilot-usage-metrics/copilot-metrics). ## Using {% data variables.copilot.copilot_chat_short %} to analyze exported data @@ -39,6 +39,6 @@ For deeper analysis, you can export NDJSON reports from the dashboard and use {% ## Next steps -* To learn how to interpret the data in each chart and act on usage trends, see [AUTOTITLE](/copilot/reference/interpret-copilot-metrics). +* To learn how to interpret the data in each chart and act on usage trends, see [AUTOTITLE](/copilot/reference/copilot-usage-metrics/interpret-copilot-metrics). * To learn how to track license activation and initial usage of {% data variables.product.prodname_copilot %} with usage metrics, see [AUTOTITLE](/copilot/tutorials/roll-out-at-scale/assign-licenses/track-usage-and-adoption). * To access usage data programmatically, see [AUTOTITLE](/rest/copilot/copilot-usage-metrics). diff --git a/content/copilot/how-tos/chat-with-copilot/chat-in-ide.md b/content/copilot/how-tos/chat-with-copilot/chat-in-ide.md index 970e0c4265f6..020b81ada501 100644 --- a/content/copilot/how-tos/chat-with-copilot/chat-in-ide.md +++ b/content/copilot/how-tos/chat-with-copilot/chat-in-ide.md @@ -23,7 +23,7 @@ category: ## Introduction -This guide describes how to use {% data variables.copilot.copilot_chat_short %} and agents to automate coding tasks by breaking them into steps, using tools to read files, edit code, and run commands, and self-correcting when something goes wrong. You can also ask general questions about software development, or specific questions about the code in your project. For more information, see [AUTOTITLE](/copilot/concepts/about-github-copilot-chat). +This guide describes how to use {% data variables.copilot.copilot_chat_short %} and agents to automate coding tasks by breaking them into steps, using tools to read files, edit code, and run commands, and self-correcting when something goes wrong. You can also ask general questions about software development, or specific questions about the code in your project. For more information, see [AUTOTITLE](/copilot/concepts/chat). @@ -77,7 +77,7 @@ For more information, see [Chat overview](https://aka.ms/vscode-copilot-agent) i 1. In the {% data variables.copilot.copilot_chat_short %} window, click the tools icon. 1. Enable the `runSubagent` tool. -If you use custom prompt files or {% data variables.copilot.custom_agents_short %}, ensure you specify the `runSubagent` tool in the `tools` frontmatter property. See [AUTOTITLE](/copilot/how-tos/use-copilot-agents/cloud-agent/create-custom-agents#creating-a-custom-agent-profile-in-visual-studio-code), and [Use prompt files in VS Code](https://code.visualstudio.com/docs/copilot/customization/prompt-files) in the {% data variables.product.prodname_vscode %} documentation. +If you use custom prompt files or {% data variables.copilot.custom_agents_short %}, ensure you specify the `runSubagent` tool in the `tools` frontmatter property. See [AUTOTITLE](/copilot/how-tos/copilot-on-github/customize-copilot/customize-cloud-agent/create-custom-agents#creating-a-custom-agent-profile-in-visual-studio-code), and [Use prompt files in VS Code](https://code.visualstudio.com/docs/copilot/customization/prompt-files) in the {% data variables.product.prodname_vscode %} documentation. #### Invoking {% data variables.copilot.subagents_short %} @@ -132,17 +132,17 @@ You can give the agent a high-level description of what you want to build and it ![Screenshot of the '{% data variables.copilot.copilot_chat_short %}' button, highlighted with a dark orange outline.](/assets/images/help/copilot/vsc-copilot-chat-icon.png) -1. Enter a prompt in the prompt box. For an introduction to the kinds of prompts you can use, see [AUTOTITLE](/copilot/get-started/getting-started-with-prompts-for-copilot-chat). +1. Enter a prompt in the prompt box. For an introduction to the kinds of prompts you can use, see [AUTOTITLE](/copilot/how-tos/chat-with-copilot/get-started-with-chat-in-your-ide). 1. Evaluate {% data variables.product.prodname_copilot_short %}'s response, and make a follow-up request if needed. The response may contain text, code blocks, buttons, images, URIs, and file trees. The response often includes interactive elements. For example, the response may include a menu to insert a code block, or a button to invoke a {% data variables.product.prodname_vscode %} command. - To see the files that {% data variables.copilot.copilot_chat_short %} used to generate the response, select the **Used _n_ references** dropdown at the top of the response. The references may include a link to a custom instructions file for your repository. This file contains additional information that is automatically added to all of your chat questions to improve the quality of the responses. For more information, see [AUTOTITLE](/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot). + To see the files that {% data variables.copilot.copilot_chat_short %} used to generate the response, select the **Used _n_ references** dropdown at the top of the response. The references may include a link to a custom instructions file for your repository. This file contains additional information that is automatically added to all of your chat questions to improve the quality of the responses. For more information, see [AUTOTITLE](/copilot/how-tos/copilot-on-github/customize-copilot/add-custom-instructions/add-repository-instructions). ## Using keywords in your prompt -You can use special keywords to help {% data variables.product.prodname_copilot_short %} understand your prompt. For examples, see [AUTOTITLE](/copilot/get-started/getting-started-with-prompts-for-copilot-chat). +You can use special keywords to help {% data variables.product.prodname_copilot_short %} understand your prompt. For examples, see [AUTOTITLE](/copilot/how-tos/chat-with-copilot/get-started-with-chat-in-your-ide). ### Chat participants @@ -154,19 +154,19 @@ Chat participants are like domain experts who have a specialty that they can hel Alternatively, you can manually specify a chat participant to scope your prompt to a specific domain. To do this, type `@` in the chat prompt box, followed by a chat participant name. -For a list of available chat participants, type `@` in the chat prompt box. See also [AUTOTITLE](/copilot/using-github-copilot/github-copilot-chat-cheat-sheet?tool=vscode#chat-participants) or [Chat participants](https://code.visualstudio.com/docs/copilot/copilot-chat#_chat-participants) in the {% data variables.product.prodname_vscode %} documentation. +For a list of available chat participants, type `@` in the chat prompt box. See also [AUTOTITLE](/copilot/reference/chat-cheat-sheet?tool=vscode#chat-participants) or [Chat participants](https://code.visualstudio.com/docs/copilot/copilot-chat#_chat-participants) in the {% data variables.product.prodname_vscode %} documentation. ### Slash commands Use slash commands to avoid writing complex prompts for common scenarios. To use a slash command, type `/` in the chat prompt box, followed by a command. -To see all available slash commands, type `/` in the chat prompt box. See also [AUTOTITLE](/copilot/using-github-copilot/github-copilot-chat-cheat-sheet?tool=vscode#slash-commands) or [Slash commands](https://code.visualstudio.com/docs/copilot/reference/copilot-vscode-features#_slash-commands) in the {% data variables.product.prodname_vscode %} documentation. +To see all available slash commands, type `/` in the chat prompt box. See also [AUTOTITLE](/copilot/reference/chat-cheat-sheet?tool=vscode#slash-commands) or [Slash commands](https://code.visualstudio.com/docs/copilot/reference/copilot-vscode-features#_slash-commands) in the {% data variables.product.prodname_vscode %} documentation. ### Chat variables Use chat variables to include specific context in your prompt. To use a chat variable, type `#` in the chat prompt box, followed by a chat variable. -To see all available chat variables, type `#` in the chat prompt box. See also [AUTOTITLE](/copilot/using-github-copilot/github-copilot-chat-cheat-sheet?tool=vscode#chat-variables). +To see all available chat variables, type `#` in the chat prompt box. See also [AUTOTITLE](/copilot/reference/chat-cheat-sheet?tool=vscode#chat-variables). ## Using {% data variables.product.prodname_dotcom %} skills for {% data variables.product.prodname_copilot_short %} @@ -212,11 +212,11 @@ To leave feedback about the {% data variables.copilot.copilot_chat %} extension, ## Further reading -* [AUTOTITLE](/copilot/using-github-copilot/prompt-engineering-for-github-copilot) +* [AUTOTITLE](/copilot/concepts/prompting/prompt-engineering) * [Using {% data variables.copilot.copilot_chat_short %} in {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/copilot/copilot-chat) and [Getting started with {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/copilot/getting-started) in the {% data variables.product.prodname_vscode %} documentation * [AUTOTITLE](/copilot/how-tos/copilot-on-github/use-copilot-agents/manage-and-track-agents) -* [AUTOTITLE](/copilot/github-copilot-enterprise/copilot-chat-in-github/using-github-copilot-chat-in-githubcom) -* [AUTOTITLE](/copilot/github-copilot-chat/about-github-copilot-chat) +* [AUTOTITLE](/copilot/how-tos/copilot-on-github/chat-with-copilot/chat-in-github) +* [AUTOTITLE](/copilot/responsible-use/chat) * [AUTOTITLE](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot) * [{% data variables.product.prodname_copilot %} Trust Center](https://copilot.github.trust.page) * [{% data variables.product.prodname_copilot %} FAQ](https://github.com/features/copilot#faq) @@ -238,7 +238,7 @@ To leave feedback about the {% data variables.copilot.copilot_chat %} extension, * **{% data variables.copilot.copilot_chat %} extension**. See [Install {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vs %}](https://learn.microsoft.com/visualstudio/ide/visual-studio-github-copilot-install-and-states?ref_product=copilot&ref_type=engagement&ref_style=text) in the {% data variables.product.prodname_vs %} documentation. _{% data variables.product.prodname_vs %} 17.10 and later have the {% data variables.product.prodname_copilot %} and {% data variables.copilot.copilot_chat %} extensions built in. You don't need to install them separately._ -* **Sign in to {% data variables.product.company_short %} in {% data variables.product.prodname_vs %}**. If you experience authentication issues, see [AUTOTITLE](/copilot/troubleshooting-github-copilot/troubleshooting-issues-with-github-copilot-chat#troubleshooting-authentication-issues-in-your-editor). +* **Sign in to {% data variables.product.company_short %} in {% data variables.product.prodname_vs %}**. If you experience authentication issues, see [AUTOTITLE](/copilot/how-tos/troubleshoot-copilot/troubleshoot-common-issues#troubleshooting-authentication-issues-in-your-editor). {% data reusables.copilot.chat-access-denied %} @@ -247,12 +247,12 @@ To leave feedback about the {% data variables.copilot.copilot_chat %} extension, You can ask {% data variables.copilot.copilot_chat_short %} to give you code suggestions, explain code, generate unit tests, and suggest code fixes. 1. In the {% data variables.product.prodname_vs %} menu bar, click **View**, then click **{% data variables.copilot.copilot_chat %}**. -1. In the {% data variables.copilot.copilot_chat_short %} window, enter a prompt, then press **Enter**. For example prompts, see [AUTOTITLE](/copilot/get-started/getting-started-with-prompts-for-copilot-chat). +1. In the {% data variables.copilot.copilot_chat_short %} window, enter a prompt, then press **Enter**. For example prompts, see [AUTOTITLE](/copilot/how-tos/chat-with-copilot/get-started-with-chat-in-your-ide). 1. Evaluate {% data variables.product.prodname_copilot_short %}'s response, and submit a follow up prompt if needed. The response often includes interactive elements. For example, the response may include buttons to copy, insert, or preview the result of a code block. - To see the files that {% data variables.copilot.copilot_chat_short %} used to generate the response, click the **References** link below the response. The references may include a link to a custom instructions file for your repository. This file contains additional information that is automatically added to all of your chat questions to improve the quality of the responses. For more information, see [AUTOTITLE](/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot). + To see the files that {% data variables.copilot.copilot_chat_short %} used to generate the response, click the **References** link below the response. The references may include a link to a custom instructions file for your repository. This file contains additional information that is automatically added to all of your chat questions to improve the quality of the responses. For more information, see [AUTOTITLE](/copilot/how-tos/copilot-on-github/customize-copilot/add-custom-instructions/add-repository-instructions). ## Using keywords in your prompt @@ -262,13 +262,13 @@ You can use special keywords to help {% data variables.product.prodname_copilot_ Use slash commands to avoid writing complex prompts for common scenarios. To use a slash command, type `/` in the chat prompt box, followed by a command. -To see all available slash commands, type `/` in the chat prompt box. See also [AUTOTITLE](/copilot/using-github-copilot/github-copilot-chat-cheat-sheet?tool=vscode#slash-commands) or [Slash commands](https://learn.microsoft.com/visualstudio/ide/copilot-chat-context#slash-commands) in the {% data variables.product.prodname_vs %} documentation. +To see all available slash commands, type `/` in the chat prompt box. See also [AUTOTITLE](/copilot/reference/chat-cheat-sheet?tool=vscode#slash-commands) or [Slash commands](https://learn.microsoft.com/visualstudio/ide/copilot-chat-context#slash-commands) in the {% data variables.product.prodname_vs %} documentation. ### References By default, {% data variables.copilot.copilot_chat_short %} will reference the file that you have open or the code that you have selected. You can also use `#` followed by a file name, file name and line numbers, or `solution` to reference a specific file, lines, or solution. -See also [AUTOTITLE](/copilot/using-github-copilot/github-copilot-chat-cheat-sheet?tool=visualstudio#references) or [Reference](https://learn.microsoft.com/visualstudio/ide/copilot-chat-context#reference) in the {% data variables.product.prodname_vs %} documentation. +See also [AUTOTITLE](/copilot/reference/chat-cheat-sheet?tool=visualstudio#references) or [Reference](https://learn.microsoft.com/visualstudio/ide/copilot-chat-context#reference) in the {% data variables.product.prodname_vs %} documentation. ## Using {% data variables.product.prodname_dotcom %} skills for {% data variables.product.prodname_copilot_short %} (preview) @@ -345,11 +345,11 @@ To share feedback about {% data variables.copilot.copilot_chat_short %}, you can ## Further reading -* [AUTOTITLE](/copilot/using-github-copilot/prompt-engineering-for-github-copilot) +* [AUTOTITLE](/copilot/concepts/prompting/prompt-engineering) * [Using {% data variables.copilot.copilot_chat %} in {% data variables.product.prodname_vs %} in the Microsoft Learn documentation](https://learn.microsoft.com/visualstudio/ide/visual-studio-github-copilot-chat?view=vs-2022#use-copilot-chat-in-visual-studio) * [Tips to improve {% data variables.copilot.copilot_chat %} results in the Microsoft Learn documentation](https://learn.microsoft.com/en-us/visualstudio/ide/copilot-chat-context?view=vs-2022) -* [AUTOTITLE](/copilot/github-copilot-enterprise/copilot-chat-in-github/using-github-copilot-chat-in-githubcom) -* [AUTOTITLE](/copilot/github-copilot-chat/about-github-copilot-chat) +* [AUTOTITLE](/copilot/how-tos/copilot-on-github/chat-with-copilot/chat-in-github) +* [AUTOTITLE](/copilot/responsible-use/chat) * [AUTOTITLE](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot) * [{% data variables.product.prodname_copilot %} Trust Center](https://copilot.github.trust.page) * [{% data variables.product.prodname_copilot %} FAQ](https://github.com/features/copilot#faq) @@ -395,13 +395,13 @@ You can ask {% data variables.copilot.copilot_chat_short %} to give you code sug ![Screenshot of the {% data variables.copilot.copilot_chat %} icon in the Activity Bar.](/assets/images/help/copilot/jetbrains-copilot-chat-icon.png) -1. Enter a prompt in the prompt box. For example prompts, see [AUTOTITLE](/copilot/get-started/getting-started-with-prompts-for-copilot-chat). +1. Enter a prompt in the prompt box. For example prompts, see [AUTOTITLE](/copilot/how-tos/chat-with-copilot/get-started-with-chat-in-your-ide). 1. Evaluate {% data variables.product.prodname_copilot_short %}'s response, and submit a follow up prompt if needed. The response often includes interactive elements. For example, the response may include buttons to copy or insert a code block. - To see the files that {% data variables.copilot.copilot_chat_short %} used to generate the response, click the **References** link below the response. The references may include a link to a custom instructions file for your repository. This file contains additional information that is automatically added to all of your chat questions to improve the quality of the responses. For more information, see [AUTOTITLE](/copilot/how-tos/custom-instructions/adding-repository-custom-instructions-for-github-copilot). + To see the files that {% data variables.copilot.copilot_chat_short %} used to generate the response, click the **References** link below the response. The references may include a link to a custom instructions file for your repository. This file contains additional information that is automatically added to all of your chat questions to improve the quality of the responses. For more information, see [AUTOTITLE](/copilot/how-tos/copilot-on-github/customize-copilot/add-custom-instructions/add-repository-instructions). ## Supplementing your prompt @@ -411,7 +411,7 @@ You can use slash commands and file references to help {% data variables.product Use slash commands to avoid writing complex prompts for common scenarios. To use a slash command, type `/` in the chat prompt box, followed by a command. -To see all available slash commands, type `/` in the chat prompt box. See also [AUTOTITLE](/copilot/using-github-copilot/github-copilot-chat-cheat-sheet?tool=jetbrains#slash-commands-2). +To see all available slash commands, type `/` in the chat prompt box. See also [AUTOTITLE](/copilot/reference/chat-cheat-sheet?tool=jetbrains#slash-commands-2). ### File references @@ -471,7 +471,7 @@ Use {% data variables.copilot.copilot_edits_short %} to make changes across mult {% data reusables.copilot.subagent-intro %} -To use {% data variables.copilot.subagents_short %}, you **must have {% data variables.copilot.custom_agents_short %} configured in your environment**. See [AUTOTITLE](/copilot/how-tos/use-copilot-agents/cloud-agent/create-custom-agents). +To use {% data variables.copilot.subagents_short %}, you **must have {% data variables.copilot.custom_agents_short %} configured in your environment**. See [AUTOTITLE](/copilot/how-tos/copilot-on-github/customize-copilot/customize-cloud-agent/create-custom-agents). #### Enabling {% data variables.copilot.subagents_short %} @@ -518,10 +518,10 @@ To share feedback about {% data variables.copilot.copilot_chat_short %}, you can ## Further reading -* [AUTOTITLE](/copilot/using-github-copilot/prompt-engineering-for-github-copilot) -* [AUTOTITLE](/copilot/github-copilot-enterprise/copilot-chat-in-github/using-github-copilot-chat-in-githubcom) -* [AUTOTITLE](/copilot/github-copilot-chat/about-github-copilot-chat) -* [AUTOTITLE](/free-pro-team@latest/site-policy/github-terms/github-copilot-pre-release-terms) +* [AUTOTITLE](/copilot/concepts/prompting/prompt-engineering) +* [AUTOTITLE](/copilot/how-tos/copilot-on-github/chat-with-copilot/chat-in-github) +* [AUTOTITLE](/copilot/responsible-use/chat) +* [AUTOTITLE](/free-pro-team@latest/site-policy/github-terms/github-pre-release-license-terms) * [AUTOTITLE](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot) * [{% data variables.product.prodname_copilot %} Trust Center](https://copilot.github.trust.page) * [{% data variables.product.prodname_copilot %} FAQ](https://github.com/features/copilot#faq) @@ -537,8 +537,8 @@ To share feedback about {% data variables.copilot.copilot_chat_short %}, you can ## Prerequisites * **Access to {% data variables.product.prodname_copilot %}**. {% data reusables.copilot.subscription-prerequisite %} -* **Latest version of the {% data variables.product.prodname_copilot %} extension**. For installation instructions, see [AUTOTITLE](/copilot/configuring-github-copilot/installing-the-github-copilot-extension-in-your-environment). -* **Sign in to {% data variables.product.company_short %} in Xcode**. If you experience authentication issues, see [AUTOTITLE](/copilot/troubleshooting-github-copilot/troubleshooting-issues-with-github-copilot-chat#troubleshooting-authentication-issues-in-your-editor). +* **Latest version of the {% data variables.product.prodname_copilot %} extension**. For installation instructions, see [AUTOTITLE](/copilot/how-tos/set-up/install-copilot-extension). +* **Sign in to {% data variables.product.company_short %} in Xcode**. If you experience authentication issues, see [AUTOTITLE](/copilot/how-tos/troubleshoot-copilot/troubleshoot-common-issues#troubleshooting-authentication-issues-in-your-editor). {% data reusables.copilot.chat-access-denied %} @@ -548,13 +548,13 @@ You can ask {% data variables.copilot.copilot_chat_short %} to give you code sug 1. To open the chat window, click **Editor** in the menu bar, then click **{% data variables.product.prodname_copilot %}** then **Open Chat**. {% data variables.copilot.copilot_chat_short %} opens in a new window. -1. Enter a prompt in the prompt box. For example prompts, see [AUTOTITLE](/copilot/get-started/getting-started-with-prompts-for-copilot-chat). +1. Enter a prompt in the prompt box. For example prompts, see [AUTOTITLE](/copilot/how-tos/chat-with-copilot/get-started-with-chat-in-your-ide). 1. Evaluate {% data variables.product.prodname_copilot_short %}'s response, and submit a follow up prompt if needed. The response often includes interactive elements. For example, the response may include buttons to copy or insert a code block. - To see the files that {% data variables.copilot.copilot_chat_short %} used to generate the response, click the **References** link below the response. The references may include a link to a custom instructions file for your repository. This file contains additional information that is automatically added to all of your chat questions to improve the quality of the responses. For more information, see [AUTOTITLE](/copilot/how-tos/custom-instructions/adding-repository-custom-instructions-for-github-copilot). + To see the files that {% data variables.copilot.copilot_chat_short %} used to generate the response, click the **References** link below the response. The references may include a link to a custom instructions file for your repository. This file contains additional information that is automatically added to all of your chat questions to improve the quality of the responses. For more information, see [AUTOTITLE](/copilot/how-tos/copilot-on-github/customize-copilot/add-custom-instructions/add-repository-instructions). ## Using Model Context Protocol (MCP) servers @@ -572,7 +572,7 @@ You can use special keywords to help {% data variables.product.prodname_copilot_ Use slash commands to avoid writing complex prompts for common scenarios. To use a slash command, type `/` in the chat prompt box, followed by a command. -To see all available slash commands, type `/` in the chat prompt box. For more information, see [AUTOTITLE](/copilot/using-github-copilot/github-copilot-chat-cheat-sheet?tool=xcode#slash-commands). +To see all available slash commands, type `/` in the chat prompt box. For more information, see [AUTOTITLE](/copilot/reference/chat-cheat-sheet?tool=xcode#slash-commands). ## Using plan mode @@ -613,7 +613,7 @@ To use plan mode: {% data reusables.copilot.subagent-intro %} -To use {% data variables.copilot.subagents_short %}, you **must have {% data variables.copilot.custom_agents_short %} configured in your environment**. See [AUTOTITLE](/copilot/how-tos/use-copilot-agents/cloud-agent/create-custom-agents). +To use {% data variables.copilot.subagents_short %}, you **must have {% data variables.copilot.custom_agents_short %} configured in your environment**. See [AUTOTITLE](/copilot/how-tos/copilot-on-github/customize-copilot/customize-cloud-agent/create-custom-agents). #### Enabling {% data variables.copilot.subagents_short %} @@ -640,10 +640,10 @@ To indicate whether a response was helpful, use {% octicon "thumbsup" aria-label ## Further reading -* [AUTOTITLE](/copilot/using-github-copilot/prompt-engineering-for-github-copilot) -* [AUTOTITLE](/copilot/github-copilot-enterprise/copilot-chat-in-github/using-github-copilot-chat-in-githubcom) -* [AUTOTITLE](/copilot/github-copilot-chat/about-github-copilot-chat) -* [AUTOTITLE](/free-pro-team@latest/site-policy/github-terms/github-copilot-pre-release-terms) +* [AUTOTITLE](/copilot/concepts/prompting/prompt-engineering) +* [AUTOTITLE](/copilot/how-tos/copilot-on-github/chat-with-copilot/chat-in-github) +* [AUTOTITLE](/copilot/responsible-use/chat) +* [AUTOTITLE](/free-pro-team@latest/site-policy/github-terms/github-pre-release-license-terms) * [AUTOTITLE](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot) * [{% data variables.product.prodname_copilot %} Trust Center](https://copilot.github.trust.page) * [{% data variables.product.prodname_copilot %} FAQ](https://github.com/features/copilot#faq) @@ -659,8 +659,8 @@ To indicate whether a response was helpful, use {% octicon "thumbsup" aria-label ## Prerequisites {% data reusables.copilot.eclipse-prerequisites %} -* **Latest version of the {% data variables.product.prodname_copilot %} extension**. Download this from the [Eclipse Marketplace](https://aka.ms/copiloteclipse?ref_product=copilot&ref_type=engagement&ref_style=text). For more information, see [AUTOTITLE](/copilot/managing-copilot/configure-personal-settings/installing-the-github-copilot-extension-in-your-environment?tool=eclipse). -* **Sign in to {% data variables.product.company_short %} in Eclipse**. If you experience authentication issues, see [AUTOTITLE](/copilot/troubleshooting-github-copilot/troubleshooting-issues-with-github-copilot-chat#troubleshooting-authentication-issues-in-your-editor). +* **Latest version of the {% data variables.product.prodname_copilot %} extension**. Download this from the [Eclipse Marketplace](https://aka.ms/copiloteclipse?ref_product=copilot&ref_type=engagement&ref_style=text). For more information, see [AUTOTITLE](/copilot/how-tos/set-up/install-copilot-extension?tool=eclipse). +* **Sign in to {% data variables.product.company_short %} in Eclipse**. If you experience authentication issues, see [AUTOTITLE](/copilot/how-tos/troubleshoot-copilot/troubleshoot-common-issues#troubleshooting-authentication-issues-in-your-editor). {% data reusables.copilot.chat-access-denied %} @@ -672,13 +672,13 @@ You can ask {% data variables.copilot.copilot_chat_short %} to give you code sug 1. Enter a prompt in the prompt box, then press Enter. - For an introduction to the kinds of prompts you can use, see [AUTOTITLE](/copilot/get-started/getting-started-with-prompts-for-copilot-chat). + For an introduction to the kinds of prompts you can use, see [AUTOTITLE](/copilot/how-tos/chat-with-copilot/get-started-with-chat-in-your-ide). 1. Evaluate {% data variables.product.prodname_copilot_short %}'s response, and make a follow up request if needed. ## Using keywords in your prompt -You can use special keywords to help {% data variables.product.prodname_copilot_short %} understand your prompt. For examples, see [AUTOTITLE](/copilot/get-started/getting-started-with-prompts-for-copilot-chat). +You can use special keywords to help {% data variables.product.prodname_copilot_short %} understand your prompt. For examples, see [AUTOTITLE](/copilot/how-tos/chat-with-copilot/get-started-with-chat-in-your-ide). ### Slash commands @@ -732,7 +732,7 @@ To use agent mode: {% data reusables.copilot.subagent-intro %} -To use {% data variables.copilot.subagents_short %}, you **must have {% data variables.copilot.custom_agents_short %} configured in your environment**. See [AUTOTITLE](/copilot/how-tos/use-copilot-agents/cloud-agent/create-custom-agents). +To use {% data variables.copilot.subagents_short %}, you **must have {% data variables.copilot.custom_agents_short %} configured in your environment**. See [AUTOTITLE](/copilot/how-tos/copilot-on-github/customize-copilot/customize-cloud-agent/create-custom-agents). #### Enabling {% data variables.copilot.subagents_short %} @@ -748,9 +748,9 @@ When the {% data variables.copilot.subagent_short %} completes its task, its res ## Further reading -* [AUTOTITLE](/copilot/using-github-copilot/prompt-engineering-for-github-copilot) -* [AUTOTITLE](/copilot/github-copilot-enterprise/copilot-chat-in-github/using-github-copilot-chat-in-githubcom) -* [AUTOTITLE](/copilot/github-copilot-chat/about-github-copilot-chat) +* [AUTOTITLE](/copilot/concepts/prompting/prompt-engineering) +* [AUTOTITLE](/copilot/how-tos/copilot-on-github/chat-with-copilot/chat-in-github) +* [AUTOTITLE](/copilot/responsible-use/chat) * [AUTOTITLE](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot) * [{% data variables.product.prodname_copilot %} Trust Center](https://copilot.github.trust.page) * [{% data variables.product.prodname_copilot %} FAQ](https://github.com/features/copilot#faq) diff --git a/content/copilot/how-tos/chat-with-copilot/chat-in-windows-terminal.md b/content/copilot/how-tos/chat-with-copilot/chat-in-windows-terminal.md index 43ef92e23634..484221756922 100644 --- a/content/copilot/how-tos/chat-with-copilot/chat-in-windows-terminal.md +++ b/content/copilot/how-tos/chat-with-copilot/chat-in-windows-terminal.md @@ -17,11 +17,11 @@ category: ## Prerequisites -* **Access to {% data variables.product.prodname_copilot %}**. See [AUTOTITLE](/copilot/about-github-copilot/what-is-github-copilot#getting-access-to-copilot). +* **Access to {% data variables.product.prodname_copilot %}**. See [AUTOTITLE](/copilot/get-started/what-is-github-copilot#getting-access-to-copilot). * **{% data variables.product.prodname_windows_terminal %} Canary installed**. For installation instructions, see [Installing {% data variables.product.prodname_windows_terminal %} Canary](https://github.com/microsoft/terminal?tab=readme-ov-file#installing-windows-terminal-canary). -* **{% data variables.product.prodname_copilot %} connected to Terminal Chat**. See [AUTOTITLE](/copilot/quickstart?tool=windowsterminal). +* **{% data variables.product.prodname_copilot %} connected to Terminal Chat**. See [AUTOTITLE](/copilot/get-started/quickstart?tool=windowsterminal). -If you have access to {% data variables.product.prodname_copilot %} via your organization or enterprise, you cannot use {% data variables.product.prodname_copilot_short %} in {% data variables.product.prodname_windows_terminal %} if your organization owner or enterprise administrator has disabled {% data variables.copilot.copilot_cli_short %}. See [AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-github-copilot-features-in-your-organization/managing-policies-for-copilot-in-your-organization). +If you have access to {% data variables.product.prodname_copilot %} via your organization or enterprise, you cannot use {% data variables.product.prodname_copilot_short %} in {% data variables.product.prodname_windows_terminal %} if your organization owner or enterprise administrator has disabled {% data variables.copilot.copilot_cli_short %}. See [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-organization/manage-policies). ## Getting command explanations and suggestions diff --git a/content/copilot/how-tos/chat-with-copilot/get-started-with-chat-in-your-ide.md b/content/copilot/how-tos/chat-with-copilot/get-started-with-chat-in-your-ide.md index da228350f8bd..bffe36e3a0ec 100644 --- a/content/copilot/how-tos/chat-with-copilot/get-started-with-chat-in-your-ide.md +++ b/content/copilot/how-tos/chat-with-copilot/get-started-with-chat-in-your-ide.md @@ -29,7 +29,7 @@ Use the tabs above to select the environment where you are using {% data variabl Open {% data variables.copilot.copilot_chat_short %} in {% data variables.product.prodname_vscode %} {% octicon "link-external" height:16 aria-label="link-external" %} -Some of the following example prompts use chat participants (preceded by `@`), slash commands (preceded by `/`), or chat variables (preceded by `#`). For more information on keywords in prompts, see [AUTOTITLE](/copilot/using-github-copilot/asking-github-copilot-questions-in-your-ide#using-keywords-in-your-prompt). +Some of the following example prompts use chat participants (preceded by `@`), slash commands (preceded by `/`), or chat variables (preceded by `#`). For more information on keywords in prompts, see [AUTOTITLE](/copilot/how-tos/chat-with-copilot/chat-in-ide#using-keywords-in-your-prompt). ## Ask general software questions @@ -207,7 +207,7 @@ You can ask {% data variables.copilot.copilot_chat_short %} questions about your * Highlight relevant lines of code. * Open the relevant file. -* Add the file as a reference. For information about how to use file references, see [AUTOTITLE](/copilot/using-github-copilot/asking-github-copilot-questions-in-your-ide?tool=jetbrains#file-references). +* Add the file as a reference. For information about how to use file references, see [AUTOTITLE](/copilot/how-tos/chat-with-copilot/chat-in-ide?tool=jetbrains#file-references). * Use the `@project` chat participant. For example: diff --git a/content/copilot/how-tos/configure-content-exclusion/exclude-content-from-copilot.md b/content/copilot/how-tos/configure-content-exclusion/exclude-content-from-copilot.md index b9b2001342c4..e714b2802033 100644 --- a/content/copilot/how-tos/configure-content-exclusion/exclude-content-from-copilot.md +++ b/content/copilot/how-tos/configure-content-exclusion/exclude-content-from-copilot.md @@ -31,7 +31,7 @@ category: You can use your repository settings to specify content in your repository that {% data variables.product.prodname_copilot %} should ignore. > [!NOTE] -> {% data variables.copilot.copilot_cli %}, {% data variables.copilot.copilot_cloud_agent %}, and Agent mode in {% data variables.copilot.copilot_chat_short %} in IDEs, do not support content exclusion. For more information about these {% data variables.product.prodname_copilot_short %} features, see [AUTOTITLE](/copilot/concepts/agents/about-copilot-cli), [AUTOTITLE](/copilot/concepts/agents/cloud-agent/about-cloud-agent), and [AUTOTITLE](/copilot/how-tos/chat-with-copilot/chat-in-ide). +> {% data variables.copilot.copilot_cli %}, {% data variables.copilot.copilot_cloud_agent %}, and Agent mode in {% data variables.copilot.copilot_chat_short %} in IDEs, do not support content exclusion. For more information about these {% data variables.product.prodname_copilot_short %} features, see [AUTOTITLE](/copilot/concepts/agents/copilot-cli/about-copilot-cli), [AUTOTITLE](/copilot/concepts/agents/cloud-agent/about-cloud-agent), and [AUTOTITLE](/copilot/how-tos/chat-with-copilot/chat-in-ide). {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -200,7 +200,7 @@ For more information, see [AUTOTITLE](/rest/copilot/copilot-content-exclusion-ma ## Further reading -* [AUTOTITLE](/copilot/concepts/content-exclusion-for-github-copilot) -* [AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-access-to-github-copilot-in-your-organization/reviewing-changes-to-content-exclusions-for-github-copilot) +* [AUTOTITLE](/copilot/concepts/context/content-exclusion) +* [AUTOTITLE](/copilot/how-tos/configure-content-exclusion/review-changes) * [Configuring content exclusion for {% data variables.product.prodname_vs %}](https://learn.microsoft.com/en-us/visualstudio/ide/visual-studio-github-copilot-admin?view=vs-2022#configure-content-exclusion) in the Microsoft Learn documentation * [AUTOTITLE](/copilot/reference/supported-surfaces-for-policies) diff --git a/content/copilot/how-tos/configure-content-exclusion/review-changes.md b/content/copilot/how-tos/configure-content-exclusion/review-changes.md index a20e9d59aaf6..b891212a887b 100644 --- a/content/copilot/how-tos/configure-content-exclusion/review-changes.md +++ b/content/copilot/how-tos/configure-content-exclusion/review-changes.md @@ -74,4 +74,4 @@ Organization and repository settings include the ability to exclude content from ## Further reading -* [AUTOTITLE](/copilot/concepts/content-exclusion-for-github-copilot) +* [AUTOTITLE](/copilot/concepts/context/content-exclusion) diff --git a/content/copilot/how-tos/configure-custom-instructions-in-your-ide/add-repository-instructions-in-your-ide.md b/content/copilot/how-tos/configure-custom-instructions-in-your-ide/add-repository-instructions-in-your-ide.md index a1f81c1adf81..fa63d6902082 100644 --- a/content/copilot/how-tos/configure-custom-instructions-in-your-ide/add-repository-instructions-in-your-ide.md +++ b/content/copilot/how-tos/configure-custom-instructions-in-your-ide/add-repository-instructions-in-your-ide.md @@ -114,7 +114,7 @@ For more information about prompt files, see [Use prompt files in {% data variab * [AUTOTITLE](/copilot/reference/custom-instructions-support) * [AUTOTITLE](/copilot/tutorials/customization-library)—a curated collection of examples -* [AUTOTITLE](/copilot/tutorials/use-custom-instructions) +* [AUTOTITLE](/copilot/tutorials/customize-code-review) {% endvscode %} @@ -198,7 +198,7 @@ For more information about prompt files, see [Use prompt files in {% data variab * [AUTOTITLE](/copilot/reference/custom-instructions-support) * [AUTOTITLE](/copilot/tutorials/customization-library)—a curated collection of examples -* [AUTOTITLE](/copilot/tutorials/use-custom-instructions) +* [AUTOTITLE](/copilot/tutorials/customize-code-review) {% endvisualstudio %} @@ -301,7 +301,7 @@ Once prompt files are saved, their instructions will apply to the current worksp * [AUTOTITLE](/copilot/reference/custom-instructions-support) * [AUTOTITLE](/copilot/tutorials/customization-library)—a curated collection of examples -* [AUTOTITLE](/copilot/tutorials/use-custom-instructions) +* [AUTOTITLE](/copilot/tutorials/customize-code-review) {% endjetbrains %} @@ -339,7 +339,7 @@ Whitespace between instructions is ignored, so the instructions can be written a * [AUTOTITLE](/copilot/reference/custom-instructions-support) * [AUTOTITLE](/copilot/tutorials/customization-library/custom-instructions)—a curated collection of examples -* [AUTOTITLE](/copilot/tutorials/use-custom-instructions) +* [AUTOTITLE](/copilot/tutorials/customize-code-review) {% endxcode %} diff --git a/content/copilot/how-tos/configure-personal-settings/authenticate-to-ghecom.md b/content/copilot/how-tos/configure-personal-settings/authenticate-to-ghecom.md index e173915a90c6..c993d43b02b3 100644 --- a/content/copilot/how-tos/configure-personal-settings/authenticate-to-ghecom.md +++ b/content/copilot/how-tos/configure-personal-settings/authenticate-to-ghecom.md @@ -71,7 +71,7 @@ If you ever need to switch to an account on {% data variables.product.prodname_d 1. Open the "{% data variables.product.prodname_copilot %} for Xcode" application. 1. Click the **Advanced** tab. 1. In the "Auth provider URL" field, enter the URL where you access {% data variables.product.github %}. For example: `https://{% data variables.enterprise.data_residency_example_domain %}`. -1. Authorize the extension by following the instructions in [Signing in to {% data variables.product.prodname_copilot %}](/copilot/managing-copilot/configure-personal-settings/installing-the-github-copilot-extension-in-your-environment?tool=xcode#signing-in-to-github-copilot). +1. Authorize the extension by following the instructions in [Signing in to {% data variables.product.prodname_copilot %}](/copilot/how-tos/set-up/install-copilot-extension?tool=xcode#signing-in-to-github-copilot). {% endxcode %} diff --git a/content/copilot/how-tos/configure-personal-settings/configure-in-ide.md b/content/copilot/how-tos/configure-personal-settings/configure-in-ide.md index 8bb1811f307f..e9aba8a8d725 100644 --- a/content/copilot/how-tos/configure-personal-settings/configure-in-ide.md +++ b/content/copilot/how-tos/configure-personal-settings/configure-in-ide.md @@ -27,7 +27,7 @@ If you use a JetBrains IDE, {% data variables.product.prodname_copilot %} can he ## Prerequisites -To configure {% data variables.product.prodname_copilot %} in a JetBrains IDE, you must install the {% data variables.product.prodname_copilot %} plugin. For more information, see [AUTOTITLE](/copilot/managing-copilot/configure-personal-settings/installing-the-github-copilot-extension-in-your-environment?tool=jetbrains). +To configure {% data variables.product.prodname_copilot %} in a JetBrains IDE, you must install the {% data variables.product.prodname_copilot %} plugin. For more information, see [AUTOTITLE](/copilot/how-tos/set-up/install-copilot-extension?tool=jetbrains). ## Enabling or disabling {% data variables.product.prodname_copilot %} @@ -43,7 +43,7 @@ You can enable or disable {% data variables.product.prodname_copilot %} from wit ## Rebinding keyboard shortcuts -You can use the default keyboard shortcuts for inline suggestions in your JetBrains IDE when using {% data variables.product.prodname_copilot %}. For a list of default keyboard shortcuts, see [AUTOTITLE](/copilot/reference/keyboard-shortcuts-for-github-copilot-in-the-ide). +You can use the default keyboard shortcuts for inline suggestions in your JetBrains IDE when using {% data variables.product.prodname_copilot %}. For a list of default keyboard shortcuts, see [AUTOTITLE](/copilot/reference/keyboard-shortcuts). Alternatively, you can rebind the shortcuts to your preferred keyboard shortcuts for each specific command. For more information on rebinding keyboard shortcuts in your JetBrains IDE, see the JetBrains documentation. For example, you can view the [IntelliJ IDEA](https://www.jetbrains.com/help/idea/mastering-keyboard-shortcuts.html#choose-keymap) documentation. @@ -174,11 +174,11 @@ If you use {% data variables.product.prodname_vs %}, {% data variables.product.p ## Prerequisites -To configure {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vs %}, you must install the {% data variables.product.prodname_copilot %} plugin. For more information, see [AUTOTITLE](/copilot/configuring-github-copilot/installing-the-github-copilot-extension-in-your-environment?tool=visualstudio). +To configure {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vs %}, you must install the {% data variables.product.prodname_copilot %} plugin. For more information, see [AUTOTITLE](/copilot/how-tos/set-up/install-copilot-extension?tool=visualstudio). ## Rebinding keyboard shortcuts -You can use the default keyboard shortcuts for inline suggestions in {% data variables.product.prodname_vs %} when using {% data variables.product.prodname_copilot %}. For a list of default keyboard shortcuts, see [AUTOTITLE](/copilot/reference/keyboard-shortcuts-for-github-copilot-in-the-ide). +You can use the default keyboard shortcuts for inline suggestions in {% data variables.product.prodname_vs %} when using {% data variables.product.prodname_copilot %}. For a list of default keyboard shortcuts, see [AUTOTITLE](/copilot/reference/keyboard-shortcuts). If you don't want to use the default keyboard shortcuts in {% data variables.product.prodname_vs %} when using {% data variables.product.prodname_copilot %}, you can rebind the shortcuts in the Keyboard editor using your preferred keyboard shortcuts for each specific command. @@ -231,7 +231,7 @@ You can learn more about scenarios and setup in the [{% data variables.product.p ## Rebinding keyboard shortcuts -You can use the default keyboard shortcuts for inline suggestions in {% data variables.product.prodname_vscode_shortname %} when using {% data variables.product.prodname_copilot %}. Search keyboard shortcuts by command name in the Keyboard Shortcuts editor. For a list of default keyboard shortcuts, see [AUTOTITLE](/copilot/reference/keyboard-shortcuts-for-github-copilot-in-the-ide). +You can use the default keyboard shortcuts for inline suggestions in {% data variables.product.prodname_vscode_shortname %} when using {% data variables.product.prodname_copilot %}. Search keyboard shortcuts by command name in the Keyboard Shortcuts editor. For a list of default keyboard shortcuts, see [AUTOTITLE](/copilot/reference/keyboard-shortcuts). Alternatively, you can rebind the shortcut for each command in the Keyboard Shortcuts editor. For more information, see the [{% data variables.product.prodname_vscode %} documentation on editing shortcuts](https://code.visualstudio.com/Docs/editor/keybindings). @@ -328,11 +328,11 @@ If you use Xcode, {% data variables.product.prodname_copilot %} can help you wit ## Prerequisites -To configure {% data variables.product.prodname_copilot %} for Xcode, you must install the {% data variables.product.prodname_copilot %} extension. See [AUTOTITLE](/copilot/managing-copilot/configure-personal-settings/installing-the-github-copilot-extension-in-your-environment?tool=xcode). +To configure {% data variables.product.prodname_copilot %} for Xcode, you must install the {% data variables.product.prodname_copilot %} extension. See [AUTOTITLE](/copilot/how-tos/set-up/install-copilot-extension?tool=xcode). ## Rebinding keyboard shortcuts -You can use the default keyboard shortcuts for inline suggestions in Xcode when using {% data variables.product.prodname_copilot %}. For a list of default keyboard shortcuts, see [AUTOTITLE](/copilot/reference/keyboard-shortcuts-for-github-copilot-in-the-ide). +You can use the default keyboard shortcuts for inline suggestions in Xcode when using {% data variables.product.prodname_copilot %}. For a list of default keyboard shortcuts, see [AUTOTITLE](/copilot/reference/keyboard-shortcuts). If you don't want to use the default keyboard shortcuts for {% data variables.product.prodname_copilot %}, you can rebind the shortcuts in the Key Bindings editor and use your preferred keyboard shortcuts. @@ -378,11 +378,11 @@ After you install {% data variables.product.prodname_copilot %} in Eclipse, you ## Prerequisites -To configure {% data variables.product.prodname_copilot %} in Eclipse, you must install the {% data variables.product.prodname_copilot %} extension. See [AUTOTITLE](/copilot/configuring-github-copilot/installing-the-github-copilot-extension-in-your-environment?tool=eclipse). +To configure {% data variables.product.prodname_copilot %} in Eclipse, you must install the {% data variables.product.prodname_copilot %} extension. See [AUTOTITLE](/copilot/how-tos/set-up/install-copilot-extension?tool=eclipse). ## Rebinding keyboard shortcuts -If you don't want to use the default keyboard shortcuts for {% data variables.product.prodname_copilot %}, you can rebind the shortcuts in the Key Bindings editor and use your preferred keyboard shortcuts. For a list of default keyboard shortcuts, see [AUTOTITLE](/copilot/reference/keyboard-shortcuts-for-github-copilot-in-the-ide). +If you don't want to use the default keyboard shortcuts for {% data variables.product.prodname_copilot %}, you can rebind the shortcuts in the Key Bindings editor and use your preferred keyboard shortcuts. For a list of default keyboard shortcuts, see [AUTOTITLE](/copilot/reference/keyboard-shortcuts). 1. In the IDE, click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}** to open the menu. 1. Click **Edit Keyboard Shortcuts...** to rebind the shortcuts. diff --git a/content/copilot/how-tos/configure-personal-settings/configure-network-settings.md b/content/copilot/how-tos/configure-personal-settings/configure-network-settings.md index cfec67cd01bc..f6587a8c912c 100644 --- a/content/copilot/how-tos/configure-personal-settings/configure-network-settings.md +++ b/content/copilot/how-tos/configure-personal-settings/configure-network-settings.md @@ -20,7 +20,7 @@ category: {% endvisualstudio %} -You can connect to {% data variables.product.prodname_copilot_short %} through an HTTP proxy and use custom certificates. This is useful if you're working on a corporate network that requires a proxy server or if you need to inspect the contents of {% data variables.product.prodname_copilot_short %}'s secure connection. See [AUTOTITLE](/copilot/concepts/network-settings-for-github-copilot). +You can connect to {% data variables.product.prodname_copilot_short %} through an HTTP proxy and use custom certificates. This is useful if you're working on a corporate network that requires a proxy server or if you need to inspect the contents of {% data variables.product.prodname_copilot_short %}'s secure connection. See [AUTOTITLE](/copilot/concepts/network-settings). ## Configuring proxy settings for {% data variables.product.prodname_copilot_short %} @@ -36,13 +36,13 @@ You can configure an HTTP proxy for {% data variables.product.prodname_copilot_s > [!WARNING] Ignoring certificate errors can cause security issues and is not recommended. -If you have configured a proxy but are still encountering connection errors, see [AUTOTITLE](/copilot/troubleshooting-github-copilot/troubleshooting-network-errors-for-github-copilot#troubleshooting-proxy-errors). +If you have configured a proxy but are still encountering connection errors, see [AUTOTITLE](/copilot/how-tos/troubleshoot-copilot/troubleshoot-network-errors#troubleshooting-proxy-errors). ### Basic authentication {% data variables.product.prodname_copilot_short %} for JetBrains supports basic authentication. To authenticate, you can select **Proxy authentication** on the "Manual proxy configuration" page, then enter your credentials. -This stores your credentials as plaintext in your editor's settings. Alternatively, you may prefer to include your credentials in the proxy URL (for example: `http://USERNAME:PASSWORD@10.203.0.1:5187/`), and then set this URL as one of the supported environment variables listed in [Proxy settings for {% data variables.product.prodname_copilot_short %}](/copilot/concepts/network-settings-for-github-copilot#proxy-settings-for-copilot). +This stores your credentials as plaintext in your editor's settings. Alternatively, you may prefer to include your credentials in the proxy URL (for example: `http://USERNAME:PASSWORD@10.203.0.1:5187/`), and then set this URL as one of the supported environment variables listed in [Proxy settings for {% data variables.product.prodname_copilot_short %}](/copilot/concepts/network-settings#proxy-settings-for-copilot). {% endjetbrains %} @@ -55,11 +55,11 @@ This stores your credentials as plaintext in your editor's settings. Alternative > [!WARNING] Ignoring certificate errors can cause security issues and is not recommended. -If you have configured a proxy but are still encountering connection errors, see [AUTOTITLE](/copilot/troubleshooting-github-copilot/troubleshooting-network-errors-for-github-copilot#troubleshooting-proxy-errors). +If you have configured a proxy but are still encountering connection errors, see [AUTOTITLE](/copilot/how-tos/troubleshoot-copilot/troubleshoot-network-errors#troubleshooting-proxy-errors). ### Basic authentication -{% data variables.product.prodname_copilot_short %} for {% data variables.product.prodname_vscode_shortname %} supports basic authentication. To authenticate, you can include your credentials in the proxy URL, for example: `http://USERNAME:PASSWORD@10.203.0.1:5187/`. You can store this URL in your {% data variables.product.prodname_vscode_shortname %} settings or in one of the environment variables listed in [Proxy settings for {% data variables.product.prodname_copilot_short %}](/copilot/concepts/network-settings-for-github-copilot#proxy-settings-for-copilot). +{% data variables.product.prodname_copilot_short %} for {% data variables.product.prodname_vscode_shortname %} supports basic authentication. To authenticate, you can include your credentials in the proxy URL, for example: `http://USERNAME:PASSWORD@10.203.0.1:5187/`. You can store this URL in your {% data variables.product.prodname_vscode_shortname %} settings or in one of the environment variables listed in [Proxy settings for {% data variables.product.prodname_copilot_short %}](/copilot/concepts/network-settings#proxy-settings-for-copilot). {% endvscode %} @@ -67,7 +67,7 @@ If you have configured a proxy but are still encountering connection errors, see {% data variables.product.prodname_copilot_short %} for {% data variables.product.prodname_vs %} reads the proxy settings from Windows. For information about configuring proxy settings on Windows, see the instructions under "To set up a proxy server connection manually" in [Use a proxy server in Windows](https://support.microsoft.com/en-us/windows/use-a-proxy-server-in-windows-03096c53-0554-4ffe-b6ab-8b1deee8dae1) in the Microsoft documentation. -If you have configured a proxy but are still encountering connection errors, see [AUTOTITLE](/copilot/troubleshooting-github-copilot/troubleshooting-network-errors-for-github-copilot#troubleshooting-proxy-errors). +If you have configured a proxy but are still encountering connection errors, see [AUTOTITLE](/copilot/how-tos/troubleshoot-copilot/troubleshoot-network-errors#troubleshooting-proxy-errors). ### Basic authentication @@ -82,7 +82,7 @@ If you need to authenticate to a proxy, you can try one of the below: ``` This sets the variable permanently for your user account. Restart any applications that need to use this variable. -1. You can include your credentials in the proxy URL (for example: `http://USERNAME:PASSWORD@10.203.0.1:5187/`), then set this URL as one of the supported environment variables listed in [Proxy settings for {% data variables.product.prodname_copilot_short %}](/copilot/concepts/network-settings-for-github-copilot#proxy-settings-for-copilot). +1. You can include your credentials in the proxy URL (for example: `http://USERNAME:PASSWORD@10.203.0.1:5187/`), then set this URL as one of the supported environment variables listed in [Proxy settings for {% data variables.product.prodname_copilot_short %}](/copilot/concepts/network-settings#proxy-settings-for-copilot). {% endvisualstudio %} @@ -120,4 +120,4 @@ Generally, if you're using company equipment, your company's IT department shoul * For macOS, see [Add certificates to a keychain using Keychain Access on Mac](https://support.apple.com/en-gb/guide/keychain-access/kyca2431/mac) in the Keychain Access User Guide. * For Linux, see [Installing a root CA certificate in the trust store](https://ubuntu.com/server/docs/security-trust-store) in the Ubuntu documentation. Similar instructions should apply to most Linux distributions. -If you have installed a certificate but {% data variables.product.prodname_copilot_short %} isn't detecting it, see [AUTOTITLE](/copilot/troubleshooting-github-copilot/troubleshooting-network-errors-for-github-copilot#troubleshooting-certificate-related-errors). +If you have installed a certificate but {% data variables.product.prodname_copilot_short %} isn't detecting it, see [AUTOTITLE](/copilot/how-tos/troubleshoot-copilot/troubleshoot-network-errors#troubleshooting-certificate-related-errors). diff --git a/content/copilot/how-tos/copilot-cli/cli-best-practices.md b/content/copilot/how-tos/copilot-cli/cli-best-practices.md index 03b429d6fe3c..80286aa49bdc 100644 --- a/content/copilot/how-tos/copilot-cli/cli-best-practices.md +++ b/content/copilot/how-tos/copilot-cli/cli-best-practices.md @@ -94,7 +94,7 @@ Use `/model` to choose from available models based on your task complexity: | Model | Best For | Tradeoffs | | ----- | -------- | --------- | -| **Auto** | Reduced rate limiting and lower latency and errors | See [AUTOTITLE](/copilot/concepts/auto-model-selection) | +| **Auto** | Reduced rate limiting and lower latency and errors | See [AUTOTITLE](/copilot/concepts/models/auto-model-selection) | | **Claude Opus 4.5** (default) | Complex architecture, difficult debugging, nuanced refactoring | Most capable but more costly | | **Claude Sonnet 4.5** | Day-to-day coding, most routine tasks | Fast, cost-effective, handles most work well | | **GPT-5.2 Codex** | Code generation, code review, straightforward implementations | Excellent for reviewing code produced by other models | @@ -520,7 +520,7 @@ Here is what you will learn: ## Further reading -* [AUTOTITLE](/copilot/concepts/agents/about-copilot-cli) -* [AUTOTITLE](/copilot/how-tos/use-copilot-agents/use-copilot-cli) +* [AUTOTITLE](/copilot/concepts/agents/copilot-cli/about-copilot-cli) +* [AUTOTITLE](/copilot/how-tos/copilot-cli/use-copilot-cli/overview) * [AUTOTITLE](/copilot/reference/copilot-cli-reference/cli-command-reference) * [{% data variables.product.prodname_copilot_short %} plans and pricing](https://github.com/features/copilot/plans) diff --git a/content/copilot/how-tos/copilot-cli/cli-getting-started.md b/content/copilot/how-tos/copilot-cli/cli-getting-started.md index 35c80c9fad77..971e743c9c68 100644 --- a/content/copilot/how-tos/copilot-cli/cli-getting-started.md +++ b/content/copilot/how-tos/copilot-cli/cli-getting-started.md @@ -125,7 +125,7 @@ where TOPIC is one of the topics listed in the help output. Find out more about {% data variables.copilot.copilot_cli_short %}: -* [AUTOTITLE](/copilot/concepts/agents/about-copilot-cli) -* [AUTOTITLE](/copilot/how-tos/use-copilot-agents/use-copilot-cli) +* [AUTOTITLE](/copilot/concepts/agents/copilot-cli/about-copilot-cli) +* [AUTOTITLE](/copilot/how-tos/copilot-cli/use-copilot-cli/overview) * [AUTOTITLE](/copilot/how-tos/copilot-cli/cli-best-practices) * [Get started with {% data variables.copilot.copilot_cli %}: A free hands-on course](https://developer.microsoft.com/blog/get-started-with-github-copilot-cli-a-free-hands-on-course) diff --git a/content/copilot/how-tos/copilot-cli/customize-copilot/add-custom-instructions.md b/content/copilot/how-tos/copilot-cli/customize-copilot/add-custom-instructions.md index d5a512eb210b..9a73b41121cb 100644 --- a/content/copilot/how-tos/copilot-cli/customize-copilot/add-custom-instructions.md +++ b/content/copilot/how-tos/copilot-cli/customize-copilot/add-custom-instructions.md @@ -81,4 +81,4 @@ If you make changes to your custom instructions during a CLI session, your chang * [AUTOTITLE](/copilot/reference/custom-instructions-support) * [AUTOTITLE](/copilot/tutorials/customization-library/custom-instructions)—a curated collection of examples -* [AUTOTITLE](/copilot/tutorials/use-custom-instructions) +* [AUTOTITLE](/copilot/tutorials/customize-code-review) diff --git a/content/copilot/how-tos/copilot-cli/customize-copilot/add-mcp-servers.md b/content/copilot/how-tos/copilot-cli/customize-copilot/add-mcp-servers.md index ac9bf01024c8..3e4bbae300e7 100644 --- a/content/copilot/how-tos/copilot-cli/customize-copilot/add-mcp-servers.md +++ b/content/copilot/how-tos/copilot-cli/customize-copilot/add-mcp-servers.md @@ -13,7 +13,7 @@ docsTeamMetrics: - copilot-cli --- -The Model Context Protocol (MCP) is an open standard that defines how applications share context with large language models (LLMs). You can connect MCP servers to {% data variables.copilot.copilot_cli %} to give {% data variables.product.prodname_copilot_short %} access to external tools, data sources, and services. For an overview of MCP, see [AUTOTITLE](/copilot/concepts/about-mcp). +The Model Context Protocol (MCP) is an open standard that defines how applications share context with large language models (LLMs). You can connect MCP servers to {% data variables.copilot.copilot_cli %} to give {% data variables.product.prodname_copilot_short %} access to external tools, data sources, and services. For an overview of MCP, see [AUTOTITLE](/copilot/concepts/context/mcp). ## Adding an MCP server @@ -136,7 +136,7 @@ The following example shows a configuration file with a local server and a remot } ``` -For more information on MCP server configuration, see [AUTOTITLE](/copilot/how-tos/use-copilot-agents/cloud-agent/extend-cloud-agent-with-mcp#writing-a-json-configuration-for-mcp-servers). +For more information on MCP server configuration, see [AUTOTITLE](/copilot/how-tos/copilot-on-github/customize-copilot/configure-mcp-servers#writing-a-json-configuration-for-mcp-servers). ### Searching and installing from the registry @@ -210,6 +210,6 @@ Once you have added an MCP server, {% data variables.product.prodname_copilot_sh ## Further reading -* [AUTOTITLE](/copilot/concepts/about-mcp) -* [AUTOTITLE](/copilot/how-tos/provide-context/use-mcp/extend-copilot-chat-with-mcp) -* [AUTOTITLE](/copilot/how-tos/use-copilot-agents/cloud-agent/extend-cloud-agent-with-mcp) +* [AUTOTITLE](/copilot/concepts/context/mcp) +* [AUTOTITLE](/copilot/how-tos/provide-context/use-mcp-in-your-ide/extend-copilot-chat-with-mcp) +* [AUTOTITLE](/copilot/how-tos/copilot-on-github/customize-copilot/configure-mcp-servers) diff --git a/content/copilot/how-tos/copilot-cli/customize-copilot/plugins-creating.md b/content/copilot/how-tos/copilot-cli/customize-copilot/plugins-creating.md index 93fbb2f5a005..f42ba006c413 100644 --- a/content/copilot/how-tos/copilot-cli/customize-copilot/plugins-creating.md +++ b/content/copilot/how-tos/copilot-cli/customize-copilot/plugins-creating.md @@ -47,7 +47,7 @@ my-plugin/ {% data reusables.copilot.copilot-cli.cli-example-plugin-file %} - For details of the full set of fields you can include in this file, see [AUTOTITLE](/copilot/reference/cli-plugin-reference#pluginjson). + For details of the full set of fields you can include in this file, see [AUTOTITLE](/copilot/reference/copilot-cli-reference/cli-plugin-reference#pluginjson). 1. Add some components to your plugin by creating the appropriate files and directories for agents, skills, hooks, and MCP server configurations. @@ -138,4 +138,4 @@ To distribute your plugin, you can add it to a marketplace. See [AUTOTITLE](/cop ## Further reading * [AUTOTITLE](/copilot/how-tos/copilot-cli/customize-copilot/plugins-finding-installing) -* [AUTOTITLE](/copilot/reference/cli-plugin-reference) +* [AUTOTITLE](/copilot/reference/copilot-cli-reference/cli-plugin-reference) diff --git a/content/copilot/how-tos/copilot-cli/customize-copilot/plugins-marketplace.md b/content/copilot/how-tos/copilot-cli/customize-copilot/plugins-marketplace.md index 6554633d3711..dd63880ce621 100644 --- a/content/copilot/how-tos/copilot-cli/customize-copilot/plugins-marketplace.md +++ b/content/copilot/how-tos/copilot-cli/customize-copilot/plugins-marketplace.md @@ -44,7 +44,7 @@ You have created one or more plugins that you want to share. See [AUTOTITLE](/co {% data reusables.copilot.copilot-cli.cli-path-to-plugins %} - For details of the full set of fields you can include in this file, see [AUTOTITLE](/copilot/reference/cli-plugin-reference#marketplacejson). + For details of the full set of fields you can include in this file, see [AUTOTITLE](/copilot/reference/copilot-cli-reference/cli-plugin-reference#marketplacejson). 1. Add the `marketplace.json` file to the `.github/plugin` directory of a repository. @@ -63,4 +63,4 @@ You have created one or more plugins that you want to share. See [AUTOTITLE](/co ## Further reading * [AUTOTITLE](/copilot/how-tos/copilot-cli/customize-copilot/plugins-finding-installing) -* [AUTOTITLE](/copilot/reference/cli-plugin-reference) +* [AUTOTITLE](/copilot/reference/copilot-cli-reference/cli-plugin-reference) diff --git a/content/copilot/how-tos/copilot-cli/customize-copilot/use-hooks.md b/content/copilot/how-tos/copilot-cli/customize-copilot/use-hooks.md index d11c08814f2f..a125d6c81637 100644 --- a/content/copilot/how-tos/copilot-cli/customize-copilot/use-hooks.md +++ b/content/copilot/how-tos/copilot-cli/customize-copilot/use-hooks.md @@ -106,5 +106,5 @@ The following examples for macOS and Windows show how to configure hooks that wi * [AUTOTITLE](/copilot/reference/hooks-reference) * [AUTOTITLE](/copilot/concepts/agents/cloud-agent/about-cloud-agent) -* [AUTOTITLE](/copilot/concepts/agents/about-copilot-cli) -* [AUTOTITLE](/copilot/how-tos/use-copilot-agents/cloud-agent/customize-the-agent-environment) +* [AUTOTITLE](/copilot/concepts/agents/copilot-cli/about-copilot-cli) +* [AUTOTITLE](/copilot/how-tos/copilot-on-github/customize-copilot/customize-cloud-agent/customize-the-agent-environment) diff --git a/content/copilot/how-tos/copilot-cli/set-up-copilot-cli/add-lsp-servers.md b/content/copilot/how-tos/copilot-cli/set-up-copilot-cli/add-lsp-servers.md index 0eff54cce2f8..3530dc658c3a 100644 --- a/content/copilot/how-tos/copilot-cli/set-up-copilot-cli/add-lsp-servers.md +++ b/content/copilot/how-tos/copilot-cli/set-up-copilot-cli/add-lsp-servers.md @@ -292,4 +292,4 @@ You can list and manage your LSP servers in an interactive CLI session using the ## Further reading * [AUTOTITLE](/copilot/how-tos/copilot-cli) -* [AUTOTITLE](/copilot/how-tos/use-copilot-agents/use-copilot-cli) +* [AUTOTITLE](/copilot/how-tos/copilot-cli/use-copilot-cli/overview) diff --git a/content/copilot/how-tos/copilot-cli/set-up-copilot-cli/configure-copilot-cli.md b/content/copilot/how-tos/copilot-cli/set-up-copilot-cli/configure-copilot-cli.md index 401593f7a40d..efc05ab0b1f5 100644 --- a/content/copilot/how-tos/copilot-cli/set-up-copilot-cli/configure-copilot-cli.md +++ b/content/copilot/how-tos/copilot-cli/set-up-copilot-cli/configure-copilot-cli.md @@ -24,7 +24,7 @@ This article shows you how to set trusted directories, configure access for tool ## Setting trusted directories -Trusted directories control where {% data variables.copilot.copilot_cli_short %} can read, modify, and execute files. Trusting a directory has security implications, see [Security considerations](/copilot/concepts/agents/about-copilot-cli#trusted-directories). +Trusted directories control where {% data variables.copilot.copilot_cli_short %} can read, modify, and execute files. Trusting a directory has security implications, see [Security considerations](/copilot/concepts/agents/copilot-cli/about-copilot-cli#trusted-directories). ### Choosing to trust a directory @@ -54,7 +54,7 @@ You can edit the list of permanently trusted directories. Trusted directories ar You can control which tools {% data variables.copilot.copilot_cli_short %} can use, either by responding to approval prompts when {% data variables.product.prodname_copilot_short %} attempts to use a tool, or by specifying permissions via command-line flags. -Be aware that allowing tool access has security implications, see [Security considerations](/copilot/concepts/agents/about-copilot-cli#allowed-tools). +Be aware that allowing tool access has security implications, see [Security considerations](/copilot/concepts/agents/copilot-cli/about-copilot-cli#allowed-tools). In this section, you can learn how to: diff --git a/content/copilot/how-tos/copilot-cli/set-up-copilot-cli/install-copilot-cli.md b/content/copilot/how-tos/copilot-cli/set-up-copilot-cli/install-copilot-cli.md index da4bdab7db13..7bdda1833672 100644 --- a/content/copilot/how-tos/copilot-cli/set-up-copilot-cli/install-copilot-cli.md +++ b/content/copilot/how-tos/copilot-cli/set-up-copilot-cli/install-copilot-cli.md @@ -23,14 +23,14 @@ docsTeamMetrics: - copilot-cli --- -To find out about {% data variables.copilot.copilot_cli_short %} before you install it, see [AUTOTITLE](/copilot/concepts/agents/about-copilot-cli). +To find out about {% data variables.copilot.copilot_cli_short %} before you install it, see [AUTOTITLE](/copilot/concepts/agents/copilot-cli/about-copilot-cli). ## Prerequisites * **An active {% data variables.product.prodname_copilot %} subscription**. See [{% data variables.product.prodname_copilot_short %} plans](https://github.com/features/copilot/plans?ref_product=copilot&ref_type=engagement&ref_style=text). * (On Windows) **PowerShell** v6 or higher -If you have access to {% data variables.product.prodname_copilot %} via your organization or enterprise, you cannot use {% data variables.copilot.copilot_cli_short %} if your organization owner or enterprise administrator has disabled it in the organization or enterprise settings. See [AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-github-copilot-features-in-your-organization/managing-policies-for-copilot-in-your-organization). +If you have access to {% data variables.product.prodname_copilot %} via your organization or enterprise, you cannot use {% data variables.copilot.copilot_cli_short %} if your organization owner or enterprise administrator has disabled it in the organization or enterprise settings. See [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-organization/manage-policies). ## Installing or updating {% data variables.copilot.copilot_cli_short %} @@ -123,6 +123,6 @@ You can also authenticate using a {% data variables.product.pat_v2 %} with the " ## Next steps -You can now use {% data variables.product.prodname_copilot_short %} from the command line. See [AUTOTITLE](/copilot/how-tos/use-copilot-agents/use-copilot-cli). +You can now use {% data variables.product.prodname_copilot_short %} from the command line. See [AUTOTITLE](/copilot/how-tos/copilot-cli/use-copilot-cli/overview). For a list of commands for {% data variables.copilot.copilot_cli_short %}, including the command to update, see [AUTOTITLE](/copilot/reference/copilot-cli-reference/cli-command-reference). diff --git a/content/copilot/how-tos/copilot-cli/use-copilot-cli/agentic-code-review.md b/content/copilot/how-tos/copilot-cli/use-copilot-cli/agentic-code-review.md index 6c691af7f0c3..df65cf2d291e 100644 --- a/content/copilot/how-tos/copilot-cli/use-copilot-cli/agentic-code-review.md +++ b/content/copilot/how-tos/copilot-cli/use-copilot-cli/agentic-code-review.md @@ -27,5 +27,5 @@ You can use the `/review` slash command to have {% data variables.product.prodna ## Further reading -* [AUTOTITLE](/copilot/how-tos/copilot-cli/automate-with-actions) -* [AUTOTITLE](/copilot/how-tos/copilot-cli/add-custom-instructions) +* [AUTOTITLE](/copilot/how-tos/copilot-cli/automate-copilot-cli/automate-with-actions) +* [AUTOTITLE](/copilot/how-tos/copilot-cli/customize-copilot/add-custom-instructions) diff --git a/content/copilot/how-tos/copilot-cli/use-copilot-cli/invoke-custom-agents.md b/content/copilot/how-tos/copilot-cli/use-copilot-cli/invoke-custom-agents.md index 88ddb8f8ef4b..1032129b676f 100644 --- a/content/copilot/how-tos/copilot-cli/use-copilot-cli/invoke-custom-agents.md +++ b/content/copilot/how-tos/copilot-cli/use-copilot-cli/invoke-custom-agents.md @@ -84,7 +84,7 @@ In the case of naming conflicts (where agents share the same filename), a user-l copilot --agent=refactor-agent --prompt "Refactor this code block" ``` -For more information, see [AUTOTITLE](/copilot/how-tos/use-copilot-agents/cloud-agent/create-custom-agents). +For more information, see [AUTOTITLE](/copilot/how-tos/copilot-on-github/customize-copilot/customize-cloud-agent/create-custom-agents). ## Use skills @@ -107,7 +107,7 @@ To extend the functionality available to you in {% data variables.copilot.copilo 1. Fill in the details for the MCP server you want to add, using the Tab key to move between fields. 1. Press Ctrl+S to save the details. -Details of your configured MCP servers are stored in the `mcp-config.json` file, which is located, by default, in the `~/.copilot` directory. This location can be changed by setting the `COPILOT_HOME` environment variable. For information about the JSON structure of a server definition, see [AUTOTITLE](/copilot/how-tos/use-copilot-agents/cloud-agent/extend-cloud-agent-with-mcp#writing-a-json-configuration-for-mcp-servers). +Details of your configured MCP servers are stored in the `mcp-config.json` file, which is located, by default, in the `~/.copilot` directory. This location can be changed by setting the `COPILOT_HOME` environment variable. For information about the JSON structure of a server definition, see [AUTOTITLE](/copilot/how-tos/copilot-on-github/customize-copilot/configure-mcp-servers#writing-a-json-configuration-for-mcp-servers). For more detailed information on adding and managing MCP servers in {% data variables.copilot.copilot_cli_short %}, see [AUTOTITLE](/copilot/how-tos/copilot-cli/customize-copilot/add-mcp-servers). diff --git a/content/copilot/how-tos/copilot-cli/use-copilot-cli/manage-pull-requests.md b/content/copilot/how-tos/copilot-cli/use-copilot-cli/manage-pull-requests.md index 72a1b63d894a..0d5a0e4ac9de 100644 --- a/content/copilot/how-tos/copilot-cli/use-copilot-cli/manage-pull-requests.md +++ b/content/copilot/how-tos/copilot-cli/use-copilot-cli/manage-pull-requests.md @@ -92,7 +92,7 @@ The `/pr` slash command has several subcommands that you can use to perform diff -Subcommands that commit and push changes will prompt you for permission before performing potentially destructive actions, unless you have pre-allowed those tools. For more information, see [AUTOTITLE](/copilot/how-tos/copilot-cli/allowing-tools). +Subcommands that commit and push changes will prompt you for permission before performing potentially destructive actions, unless you have pre-allowed those tools. For more information, see [AUTOTITLE](/copilot/how-tos/copilot-cli/use-copilot-cli/allowing-tools). ## Viewing pull request status @@ -211,6 +211,6 @@ You can append instructions to guide the pull request creation. For example: ## Further reading -* [AUTOTITLE](/copilot/how-tos/copilot-cli/allowing-tools) +* [AUTOTITLE](/copilot/how-tos/copilot-cli/use-copilot-cli/allowing-tools) * [AUTOTITLE](/copilot/how-tos/copilot-cli/use-copilot-cli/browse-issues-prs-gists) * [AUTOTITLE](/copilot/reference/copilot-cli-reference/cli-command-reference) From c518c6014d39e332be1556ce53c8840a5a8f1664 Mon Sep 17 00:00:00 2001 From: Kevin Heis Date: Thu, 9 Jul 2026 06:41:38 -0700 Subject: [PATCH 07/17] Update redirected internal links in billing (reference+tutorials) (#62125) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .../billing/reference/actions-runner-pricing.md | 4 ++-- content/billing/reference/azure-billing.md | 2 +- content/billing/reference/azure-subscription.md | 2 +- content/billing/reference/billing-roles.md | 2 +- .../billing/reference/cost-center-allocation.md | 4 ++-- .../billing/reference/costs-for-github-models.md | 2 +- .../enterprise-license-troubleshooting.md | 8 ++++---- .../billing/reference/github-license-users.md | 6 +++--- content/billing/reference/license-reports.md | 4 ++-- .../billing/reference/product-usage-included.md | 4 ++-- .../billing/reference/roles-for-visual-studio.md | 4 ++-- .../reference/supported-payment-methods.md | 16 ++++++++-------- .../tutorials/automate-usage-reporting.md | 2 +- .../billing/tutorials/control-costs-at-scale.md | 4 ++-- content/billing/tutorials/gather-insights.md | 4 ++-- content/billing/tutorials/soft-budgets.md | 2 +- 16 files changed, 35 insertions(+), 35 deletions(-) diff --git a/content/billing/reference/actions-runner-pricing.md b/content/billing/reference/actions-runner-pricing.md index fee9fc01f91a..956ea69971f6 100644 --- a/content/billing/reference/actions-runner-pricing.md +++ b/content/billing/reference/actions-runner-pricing.md @@ -61,10 +61,10 @@ redirect_from: ## Points to note about rates for runners -* The number of jobs you can run concurrently across all repositories in your user or organization account depends on your {% data variables.product.github %} plan. For more information, see [AUTOTITLE](/actions/learn-github-actions/usage-limits-billing-and-administration) for {% data variables.product.github %}-hosted runners and [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/usage-limits-for-self-hosted-runners) for self-hosted runner usage limits. +* The number of jobs you can run concurrently across all repositories in your user or organization account depends on your {% data variables.product.github %} plan. For more information, see [AUTOTITLE](/actions/concepts/billing-and-usage) for {% data variables.product.github %}-hosted runners and [AUTOTITLE](/actions/reference/limits) for self-hosted runner usage limits. * {% data reusables.actions.larger-runner-permissions %} * {% data reusables.actions.about-larger-runners-billing %} -* For {% data variables.actions.hosted_runner %}s, there is no additional cost for configurations that assign public static IP addresses to a {% data variables.actions.hosted_runner %}. For more information on {% data variables.actions.hosted_runner %}s, see [AUTOTITLE](/actions/using-github-hosted-runners/using-larger-runners/about-larger-runners). +* For {% data variables.actions.hosted_runner %}s, there is no additional cost for configurations that assign public static IP addresses to a {% data variables.actions.hosted_runner %}. For more information on {% data variables.actions.hosted_runner %}s, see [AUTOTITLE](/actions/concepts/runners/larger-runners). * Included minutes cannot be used for {% data variables.actions.hosted_runner %}s. * The {% data variables.actions.hosted_runner %}s are not free for public repositories. {% ifversion fpt or ghec %} diff --git a/content/billing/reference/azure-billing.md b/content/billing/reference/azure-billing.md index 1bab983f0942..90e43b1e3774 100644 --- a/content/billing/reference/azure-billing.md +++ b/content/billing/reference/azure-billing.md @@ -16,7 +16,7 @@ You can connect an Azure subscription to your {% data variables.product.github % Connecting an Azure subscription allows you to consolidate invoices and manage {% data variables.product.github %} spending within your organization’s existing Azure billing processes. -For details on how to connect, see [AUTOTITLE](/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription). +For details on how to connect, see [AUTOTITLE](/billing/how-tos/set-up-payment/connect-azure-sub). ## Billing cycles and invoicing diff --git a/content/billing/reference/azure-subscription.md b/content/billing/reference/azure-subscription.md index 297716c55db1..dbe2508c7415 100644 --- a/content/billing/reference/azure-subscription.md +++ b/content/billing/reference/azure-subscription.md @@ -45,4 +45,4 @@ During an **{% data variables.product.prodname_emu %} trial**, you can use meter > [!IMPORTANT] If you don't use {% data variables.product.prodname_emus %} in your trial of {% data variables.product.prodname_ghe_cloud %}, connecting an Azure subscription will immediately end your trial and begin paid usage. -For more information, see [AUTOTITLE](/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription#connecting-your-azure-subscription-to-your-enterprise-account). +For more information, see [AUTOTITLE](/billing/how-tos/set-up-payment/connect-azure-sub#connecting-your-azure-subscription-to-your-enterprise-account). diff --git a/content/billing/reference/billing-roles.md b/content/billing/reference/billing-roles.md index 0c5d4b2ebda1..ca4354a9a475 100644 --- a/content/billing/reference/billing-roles.md +++ b/content/billing/reference/billing-roles.md @@ -59,4 +59,4 @@ You can: ## Further reading * [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization) -* [AUTOTITLE](/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/roles-in-an-enterprise) +* [AUTOTITLE](/admin/managing-accounts-and-repositories/managing-roles-in-your-enterprise/abilities-of-roles) diff --git a/content/billing/reference/cost-center-allocation.md b/content/billing/reference/cost-center-allocation.md index fe70ef8e3025..816e70e62b92 100644 --- a/content/billing/reference/cost-center-allocation.md +++ b/content/billing/reference/cost-center-allocation.md @@ -48,13 +48,13 @@ Users who belong to multiple organizations in an enterprise or who receive a {% To confirm which organization is charged for a given user's license, you can request a detailed usage report. See [AUTOTITLE](/billing/reference/billing-reports#detailed-usage-report). -See [AUTOTITLE](/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-the-copilot-subscription-for-your-enterprise/about-billing-for-github-copilot-in-your-enterprise#about-seat-assignment-for-copilot-in-your-enterprise). +See [AUTOTITLE](/copilot/concepts/billing/organizations-and-enterprises#seat-assignment). ## Understanding cost center usage and attribution To view usage by cost center, go to the "Usage" page and group or filter by cost center. Any usage that is not assigned to a specific cost center is categorized as "Enterprise Only" when grouping by cost center. See [AUTOTITLE](/billing/tutorials/gather-insights). -To understand how usage for a specific resource is being attributed to cost centers, request a detailed usage report and refer to the `cost_center_name` column. See [AUTOTITLE](/billing/reference/usage-reports). +To understand how usage for a specific resource is being attributed to cost centers, request a detailed usage report and refer to the `cost_center_name` column. See [AUTOTITLE](/billing/reference/billing-reports). ## Effects of changes to cost centers diff --git a/content/billing/reference/costs-for-github-models.md b/content/billing/reference/costs-for-github-models.md index dd7b3e47ab5b..0b163947579f 100644 --- a/content/billing/reference/costs-for-github-models.md +++ b/content/billing/reference/costs-for-github-models.md @@ -17,7 +17,7 @@ The information in this article is for the direct use of {% data variables.produ {% data variables.product.github %} supports using models in two additional ways. -* {% data variables.product.prodname_copilot %} uses models to perform its work, see [AUTOTITLE](/copilot/concepts/billing/copilot-requests#model-multipliers) +* {% data variables.product.prodname_copilot %} uses models to perform its work, see [AUTOTITLE](/copilot/reference/copilot-billing/request-based-billing-legacy/copilot-requests#model-multipliers) * If you use models provided by other companies, see [AUTOTITLE](/github-models/github-models-at-scale/using-your-own-api-keys-in-github-models) ## Multipliers and costs for direct use of {% data variables.product.prodname_github_models %} diff --git a/content/billing/reference/enterprise-license-troubleshooting.md b/content/billing/reference/enterprise-license-troubleshooting.md index c322687431d4..d85d0c8eb4b0 100644 --- a/content/billing/reference/enterprise-license-troubleshooting.md +++ b/content/billing/reference/enterprise-license-troubleshooting.md @@ -15,7 +15,7 @@ category: ## People who consume a license -A person consumes a license for {% data variables.product.prodname_enterprise %} depending on specific criteria. If a user has not yet accepted an invitation to join your enterprise, the user still consumes a license. For more information about the people in your enterprise who consume a license, see [AUTOTITLE](/billing/managing-the-plan-for-your-github-account/about-per-user-pricing). +A person consumes a license for {% data variables.product.prodname_enterprise %} depending on specific criteria. If a user has not yet accepted an invitation to join your enterprise, the user still consumes a license. For more information about the people in your enterprise who consume a license, see [AUTOTITLE](/billing/reference/github-license-users). ## {% data variables.visual_studio.prodname_vs_subscriber %}s @@ -23,11 +23,11 @@ If the verified email address for the personal account of an enterprise member o > [!NOTE] For {% data variables.product.prodname_emu %} only, to make sure a user account consumes a {% data variables.product.prodname_vs %} license, ensure the {% data variables.product.prodname_vs %} UPN matches the SCIM `userName` attribute or the email address from the linked identity on the {% data variables.product.prodname_dotcom %} account. -For more information, see [AUTOTITLE](/enterprise-cloud@latest/billing/managing-billing-for-your-products/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise). +For more information, see [AUTOTITLE](/enterprise-cloud@latest/billing/concepts/enterprise-billing/visual-studio-subs). ## Users of {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} -For each user to consume a single {% ifversion enterprise-licensing-language %}license{% else %}seat{% endif %} regardless of how many deployments they use, you must synchronize license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}. For more information, see [AUTOTITLE](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud). +For each user to consume a single {% ifversion enterprise-licensing-language %}license{% else %}seat{% endif %} regardless of how many deployments they use, you must synchronize license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}. For more information, see [AUTOTITLE](/billing/how-tos/manage-server-licenses/sync-license-usage). After you synchronize license usage, {% data variables.product.prodname_dotcom %} matches user accounts on {% data variables.product.prodname_ghe_server %} with user accounts on {% data variables.product.prodname_ghe_cloud %} by email address. @@ -46,7 +46,7 @@ If your enterprise on {% data variables.product.prodname_ghe_cloud %} or any of ### Without SAML or SCIM -If there is no match with a SAML or SCIM attribute, or if SAML authentication or SCIM provisioning is not in use, we attempt to match the primary email address on {% data variables.product.prodname_ghe_server %} with a verified email address for a user account on {% data variables.product.prodname_ghe_cloud %}. For more information about verification of email addresses on {% data variables.product.prodname_ghe_cloud %}, see [AUTOTITLE](/enterprise-cloud@latest/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/verifying-your-email-address){% ifversion ghes %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %} +If there is no match with a SAML or SCIM attribute, or if SAML authentication or SCIM provisioning is not in use, we attempt to match the primary email address on {% data variables.product.prodname_ghe_server %} with a verified email address for a user account on {% data variables.product.prodname_ghe_cloud %}. For more information about verification of email addresses on {% data variables.product.prodname_ghe_cloud %}, see [AUTOTITLE](/enterprise-cloud@latest/account-and-profile/how-tos/email-preferences/verifying-your-email-address){% ifversion ghes %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %} ## Fields in the consumed license files diff --git a/content/billing/reference/github-license-users.md b/content/billing/reference/github-license-users.md index 6d9ce8033ef5..9a24af0c7d17 100644 --- a/content/billing/reference/github-license-users.md +++ b/content/billing/reference/github-license-users.md @@ -69,7 +69,7 @@ If your enterprise does not use {% data variables.product.prodname_emus %}, you * Anyone with a pending invitation to become a billing manager * Anyone who is an outside collaborator on a public repository owned by your organization, or who has a pending invitation to become one * Anyone with a failed invitation to become an organization member or an outside collaborator on a repository owned by your organization -* Guest collaborators who are not organization members or repository collaborators (see [AUTOTITLE](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#guest-collaborators)) +* Guest collaborators who are not organization members or repository collaborators (see [AUTOTITLE](/enterprise-cloud@latest/admin/managing-accounts-and-repositories/managing-roles-in-your-enterprise/abilities-of-roles#guest-collaborators)) * Users of {% data variables.visual_studio.prodname_vss_ghe %} whose accounts on {% data variables.product.prodname_dotcom %} are not linked, and who do not meet any of the other criteria for per-user pricing * Unaffiliated users: people who have been added to the enterprise, but are not members of any organizations in the enterprise * However, these users consume a bundled {% data variables.product.prodname_vs %} license if they are linked with a {% data variables.product.prodname_vs %} subscription @@ -88,8 +88,8 @@ If your enterprise does not use {% data variables.product.prodname_emus %}, you ## Further reading {%- ifversion not fpt %} -* [AUTOTITLE](/admin/overview/about-enterprise-accounts) -* [AUTOTITLE](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise) +* [AUTOTITLE](/admin/concepts/enterprise-fundamentals/enterprise-accounts) +* [AUTOTITLE](/admin/managing-accounts-and-repositories/managing-roles-in-your-enterprise/abilities-of-roles) {%- endif %} * [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization) * [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-outside-collaborators/adding-outside-collaborators-to-repositories-in-your-organization) diff --git a/content/billing/reference/license-reports.md b/content/billing/reference/license-reports.md index 1140fb7cfb44..5116e701b32f 100644 --- a/content/billing/reference/license-reports.md +++ b/content/billing/reference/license-reports.md @@ -18,7 +18,7 @@ Each license report shows information about license users in your enterprise acc {% ifversion fpt or ghec %} -* Enterprise and {% data variables.product.prodname_AS %} license users, see [AUTOTITLE](/billing/how-tos/products/download-ghas-license-use) +* Enterprise and {% data variables.product.prodname_AS %} license users, see [AUTOTITLE](/billing/how-tos/products/download-license-use) * {% data variables.product.prodname_copilot %} license users, see [AUTOTITLE](/copilot/how-tos/administer-copilot/download-activity-report) * Report using the REST API, see [AUTOTITLE](/billing/tutorials/automate-usage-reporting) @@ -26,7 +26,7 @@ If you want to generate a more detailed usage report, see [AUTOTITLE](/billing/t {% endif %} -**{% data variables.product.prodname_ghe_server %} users** can download license reports for {% data variables.product.prodname_AS %} from the **License** page under enterprise settings, see [AUTOTITLE](/billing/how-tos/products/download-ghas-license-use). +**{% data variables.product.prodname_ghe_server %} users** can download license reports for {% data variables.product.prodname_AS %} from the **License** page under enterprise settings, see [AUTOTITLE](/billing/how-tos/products/download-license-use). ## {% data variables.product.prodname_AS %} license report diff --git a/content/billing/reference/product-usage-included.md b/content/billing/reference/product-usage-included.md index ddbacbbe6a9e..60b09877f396 100644 --- a/content/billing/reference/product-usage-included.md +++ b/content/billing/reference/product-usage-included.md @@ -10,7 +10,7 @@ category: - Get started with billing --- -The table below shows the usage available in each plan. When you exceed these amounts, you'll be charged for additional usage unless you've set a budget with the setting "Stop usage when budget limit is reached" enabled. For more information, see [AUTOTITLE](/billing/tutorials/set-up-budgets). +The table below shows the usage available in each plan. When you exceed these amounts, you'll be charged for additional usage unless you've set a budget with the setting "Stop usage when budget limit is reached" enabled. For more information, see [AUTOTITLE](/billing/how-tos/set-up-budgets). @@ -95,5 +95,5 @@ The table below shows the usage available in each plan. When you exceed these am > [!TIP] > You can receive email notifications when your included usage reaches 90% and 100% during a billing period. To opt in, see [AUTOTITLE](/billing/how-tos/set-up-budgets#managing-included-usage-alerts). -For information about included requests for {% data variables.product.prodname_copilot %} plans, see [AUTOTITLE](/copilot/about-github-copilot/plans-for-github-copilot). +For information about included requests for {% data variables.product.prodname_copilot %} plans, see [AUTOTITLE](/copilot/get-started/plans). diff --git a/content/billing/reference/roles-for-visual-studio.md b/content/billing/reference/roles-for-visual-studio.md index d9f507f6cfee..6972827d6199 100644 --- a/content/billing/reference/roles-for-visual-studio.md +++ b/content/billing/reference/roles-for-visual-studio.md @@ -25,6 +25,6 @@ category: | Role | Description | More information | | :- | :- | :- | -| **Enterprise owner** | Person who has a personal account that's an administrator of an enterprise on {% data variables.location.product_location %} | [AUTOTITLE](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner){% ifversion ghes %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %} | +| **Enterprise owner** | Person who has a personal account that's an administrator of an enterprise on {% data variables.location.product_location %} | [AUTOTITLE](/enterprise-cloud@latest/admin/managing-accounts-and-repositories/managing-roles-in-your-enterprise/abilities-of-roles#enterprise-owners){% ifversion ghes %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %} | | **Organization owner** | Person who has a personal account that's an owner of an organization in your team's enterprise on {% data variables.location.product_location %} | [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners){% ifversion ghes %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %} | -| **Enterprise member** | Person who has a personal account that's a member of an enterprise on {% data variables.location.product_location %} | [AUTOTITLE](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-members) | +| **Enterprise member** | Person who has a personal account that's a member of an enterprise on {% data variables.location.product_location %} | [AUTOTITLE](/enterprise-cloud@latest/admin/managing-accounts-and-repositories/managing-roles-in-your-enterprise/abilities-of-roles#users) | diff --git a/content/billing/reference/supported-payment-methods.md b/content/billing/reference/supported-payment-methods.md index 63e1d178e9af..22bc1f50cd9c 100644 --- a/content/billing/reference/supported-payment-methods.md +++ b/content/billing/reference/supported-payment-methods.md @@ -52,18 +52,18 @@ The following Azure subscription types cannot be used as a payment method for {% {% data variables.product.github %} provides usage-based billing for the following products. -* {% data variables.product.prodname_actions %}, see [AUTOTITLE](/billing/managing-billing-for-github-actions/about-billing-for-github-actions) -* {% data variables.product.prodname_github_codespaces %}, see [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces) -* {% data variables.product.prodname_registry %}, see [AUTOTITLE](/billing/managing-billing-for-github-packages/about-billing-for-github-packages) -* {% data variables.large_files.product_name_long %}, see [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage) +* {% data variables.product.prodname_actions %}, see [AUTOTITLE](/billing/concepts/product-billing/github-actions) +* {% data variables.product.prodname_github_codespaces %}, see [AUTOTITLE](/billing/concepts/product-billing/github-codespaces) +* {% data variables.product.prodname_registry %}, see [AUTOTITLE](/billing/concepts/product-billing/github-packages) +* {% data variables.large_files.product_name_long %}, see [AUTOTITLE](/billing/concepts/product-billing/git-lfs) In addition, usage-based billing is available for the following licenses: -* {% data variables.product.prodname_enterprise %}, see [AUTOTITLE](/billing/managing-your-billing/about-billing-for-your-enterprise) -* {% data variables.product.prodname_copilot %}, see [AUTOTITLE](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot) -* {% data variables.product.prodname_GHAS %}, see [AUTOTITLE](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security) +* {% data variables.product.prodname_enterprise %}, see [AUTOTITLE](/billing/concepts/enterprise-billing/billing-for-enterprises) +* {% data variables.product.prodname_copilot %}, see [AUTOTITLE](/billing/concepts/product-billing/github-copilot-licenses) +* {% data variables.product.prodname_GHAS %}, see [AUTOTITLE](/billing/concepts/product-billing/github-advanced-security) -For information about controlling spending, see [AUTOTITLE](/billing/managing-your-billing/using-budgets-control-spending). +For information about controlling spending, see [AUTOTITLE](/billing/how-tos/set-up-budgets). > [!NOTE] > Prepaid usage is not currently available for usage-based billing through Azure. diff --git a/content/billing/tutorials/automate-usage-reporting.md b/content/billing/tutorials/automate-usage-reporting.md index 7d47d23d4bb0..818873118559 100644 --- a/content/billing/tutorials/automate-usage-reporting.md +++ b/content/billing/tutorials/automate-usage-reporting.md @@ -178,4 +178,4 @@ In some cases, you may need to calculate product-specific usage metrics from the To calculate these metrics, you typically filter usage items by `product` and `unitType`, then aggregate fields such as `quantity`, `netAmount`, and `discountAmount`. -For detailed examples and product-specific calculations, see [AUTOTITLE](/billing/reference/previous-billing-platform-endpoints). +For detailed examples and product-specific calculations, see [AUTOTITLE](/billing/get-started/introduction-to-billing). diff --git a/content/billing/tutorials/control-costs-at-scale.md b/content/billing/tutorials/control-costs-at-scale.md index 574ddf0fadd7..bc7509463924 100644 --- a/content/billing/tutorials/control-costs-at-scale.md +++ b/content/billing/tutorials/control-costs-at-scale.md @@ -313,7 +313,7 @@ The **REST API** is valuable when you: ### Options for automation -If you decide that automation would benefit your organization, the REST API examples in this tutorial provide the foundation for building custom scripts. For details of other endpoints, see [AUTOTITLE](/rest/enterprise-admin/billing?apiVersion=2022-11-28). +If you decide that automation would benefit your organization, the REST API examples in this tutorial provide the foundation for building custom scripts. For details of other endpoints, see [AUTOTITLE](/rest/billing/billing?apiVersion=2022-11-28). If you want to automate cost centers based on team membership or create a two-tier model for controlling costs of {% data variables.product.prodname_ai_credits_short %}, [{% data variables.product.github %} Cost Center Automation](https://github.com/github/cost-center-automation?ref_product=copilot&ref_type=engagement&ref_style=text) provides a complete implementation using actions workflows that you can adapt for your needs. @@ -321,7 +321,7 @@ If you want to automate cost centers based on team membership or create a two-ti To find out about the endpoints you can use to automate reporting of usage and costs, see [AUTOTITLE](/billing/tutorials/automate-usage-reporting). -If there are any paid products that you want to block all access to, you can disable the feature using an enterprise policy. See [AUTOTITLE](/admin/enforcing-policies/enforcing-policies-for-your-enterprise/about-enterprise-policies). +If there are any paid products that you want to block all access to, you can disable the feature using an enterprise policy. See [AUTOTITLE](/admin/concepts/security-and-compliance/enterprise-policies). To go deeper on the controls in this tutorial: diff --git a/content/billing/tutorials/gather-insights.md b/content/billing/tutorials/gather-insights.md index 7140eaef8aa1..f96f1349b58d 100644 --- a/content/billing/tutorials/gather-insights.md +++ b/content/billing/tutorials/gather-insights.md @@ -110,5 +110,5 @@ You can also view your active {% data variables.product.prodname_enterprise %} i ## Further reading {% ifversion ghec %} -* [AUTOTITLE](/rest/enterprise-admin/billing){% endif %} -* [AUTOTITLE](/billing/managing-your-billing/adding-licenses-to-an-organization) +* [AUTOTITLE](/rest/billing/billing){% endif %} +* [AUTOTITLE](/billing/how-tos/manage-plan-and-licenses/manage-user-licenses) diff --git a/content/billing/tutorials/soft-budgets.md b/content/billing/tutorials/soft-budgets.md index 25e6ca683ce5..21b5da0410ad 100644 --- a/content/billing/tutorials/soft-budgets.md +++ b/content/billing/tutorials/soft-budgets.md @@ -37,7 +37,7 @@ Before setting a soft budget, make a rough estimate of your expected costs. This ## 2. Set a soft budget -To set a budget for your enterprise or organization, see [AUTOTITLE](/billing/tutorials/set-up-budgets#creating-a-budget). +To set a budget for your enterprise or organization, see [AUTOTITLE](/billing/how-tos/set-up-budgets#creating-a-budget). When creating the budget, leave **Stop usage when budget limit is reached** unchecked. This choice makes the budget “soft”: you’ll receive alerts when the limit is exceeded, but usage won’t be blocked. From 7c06b1d8a446c632b1df2cf4dac7a1da70627bbb Mon Sep 17 00:00:00 2001 From: Kevin Heis Date: Thu, 9 Jul 2026 06:41:45 -0700 Subject: [PATCH 08/17] Update redirected internal links in billing (concepts+get-started+how-tos) (#62124) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- content/billing/concepts/billing-cycles.md | 12 +++++------ .../billing/concepts/budgets-and-alerts.md | 2 +- content/billing/concepts/discounted-plans.md | 6 +++--- .../billing-for-enterprises.md | 10 ++++----- .../combined-enterprise-use.md | 4 ++-- .../enterprise-billing/ghes-license-files.md | 6 +++--- .../enterprise-billing/visual-studio-subs.md | 4 ++-- .../concepts/impact-of-plan-changes.md | 10 ++++----- .../concepts/product-billing/git-lfs.md | 2 +- .../product-billing/github-actions.md | 4 ++-- .../github-advanced-security.md | 21 +++++++++---------- .../product-billing/github-code-quality.md | 4 ++-- .../product-billing/github-codespaces.md | 4 ++-- .../github-copilot-licenses.md | 6 +++--- .../concepts/product-billing/github-models.md | 12 +++++------ .../product-billing/github-packages.md | 2 +- .../concepts/product-billing/github-spark.md | 6 +++--- .../github-marketplace-apps.md | 4 ++-- .../get-started/billing-manager-onboard.md | 6 +++--- .../billing/get-started/how-billing-works.md | 8 +++---- .../get-started/introduction-to-billing.md | 12 +++++------ .../create-as-csp-partner.md | 6 +++--- .../create-client-enterprise.md | 4 ++-- .../downgrade-plan.md | 14 ++++++------- .../manage-plan-and-licenses/upgrade-plan.md | 8 +++---- .../view-enterprise-usage.md | 6 +++--- .../download-your-license.md | 4 ++-- .../sync-license-usage.md | 2 +- .../upload-new-license.md | 2 +- .../cancel-marketplace-app.md | 2 +- .../downgrade-marketplace-app.md | 4 ++-- .../pay-third-parties/end-sponsorship.md | 2 +- .../upgrade-marketplace-app.md | 2 +- .../how-tos/products/buy-advanced-security.md | 8 +++---- .../how-tos/products/download-license-use.md | 6 +++--- .../how-tos/products/estimate-spending.md | 2 +- .../how-tos/products/manage-ghas-licenses.md | 4 ++-- .../how-tos/products/use-cost-centers.md | 6 +++--- .../how-tos/products/view-ghas-committers.md | 2 +- .../products/view-productlicense-use.md | 12 +++++------ .../set-up-payment/india-one-time-payments.md | 2 +- .../manage-enterprise-invoice.md | 2 +- .../set-up-payment/set-up-vs-subscription.md | 14 ++++++------- .../how-tos/troubleshooting/declined-card.md | 4 ++-- .../enterprise-license-usage.md | 10 ++++----- .../how-tos/troubleshooting/locked-account.md | 2 +- 46 files changed, 137 insertions(+), 138 deletions(-) diff --git a/content/billing/concepts/billing-cycles.md b/content/billing/concepts/billing-cycles.md index 2562ebba43fa..e284f9847a35 100644 --- a/content/billing/concepts/billing-cycles.md +++ b/content/billing/concepts/billing-cycles.md @@ -69,10 +69,10 @@ Changes you make mid-cycle, such as adding or removing users, seats, or resource Find product-specific guidance on how usage is calculated and billed. -* [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-actions/about-billing-for-github-actions) -* [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces) -* [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-packages/about-billing-for-github-packages) -* [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-copilot/about-billing-for-github-copilot) +* [AUTOTITLE](/billing/concepts/product-billing/github-actions) +* [AUTOTITLE](/billing/concepts/product-billing/github-codespaces) +* [AUTOTITLE](/billing/concepts/product-billing/github-packages) +* [AUTOTITLE](/billing/concepts/product-billing/github-copilot-licenses) * [AUTOTITLE](/billing/concepts/product-billing/cloud-and-local-sandboxes) -* [AUTOTITLE](/billing/managing-billing-for-your-products/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise#about-licenses-for-visual-studio-subscriptions-with-github-enterprise-cloud) -* [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage) +* [AUTOTITLE](/billing/concepts/enterprise-billing/visual-studio-subs#about-licenses-for-visual-studio-subscriptions-with-github-enterprise-cloud) +* [AUTOTITLE](/billing/concepts/product-billing/git-lfs) diff --git a/content/billing/concepts/budgets-and-alerts.md b/content/billing/concepts/budgets-and-alerts.md index a8f3715cbeae..fa69bf1e789c 100644 --- a/content/billing/concepts/budgets-and-alerts.md +++ b/content/billing/concepts/budgets-and-alerts.md @@ -75,4 +75,4 @@ The maximum number of budgets per account is 10,000. ## Set up a budget -To get started with budgets, see [AUTOTITLE](/billing/tutorials/set-up-budgets). +To get started with budgets, see [AUTOTITLE](/billing/how-tos/set-up-budgets). diff --git a/content/billing/concepts/discounted-plans.md b/content/billing/concepts/discounted-plans.md index c0a823271f1a..e7f9095463d6 100644 --- a/content/billing/concepts/discounted-plans.md +++ b/content/billing/concepts/discounted-plans.md @@ -24,11 +24,11 @@ category: ## Discounts for personal accounts -In addition to the unlimited public and private repositories for students and faculty with {% data variables.product.prodname_free_user %}, verified students can apply for the {% data variables.product.prodname_student_pack %} to receive additional benefits from {% data variables.product.prodname_dotcom %} partners. For more information, see [AUTOTITLE](/free-pro-team@latest/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student). +In addition to the unlimited public and private repositories for students and faculty with {% data variables.product.prodname_free_user %}, verified students can apply for the {% data variables.product.prodname_student_pack %} to receive additional benefits from {% data variables.product.prodname_dotcom %} partners. For more information, see [AUTOTITLE](/free-pro-team@latest/education/about-github-education/github-education-for-students/apply-to-github-education-as-a-student). ## Discounts for schools and universities -Verified academic faculty can apply for {% data variables.product.prodname_team %} for teaching or academic research. For more information, see [AUTOTITLE](/free-pro-team@latest/education/explore-the-benefits-of-teaching-and-learning-with-github-education). +Verified academic faculty can apply for {% data variables.product.prodname_team %} for teaching or academic research. For more information, see [AUTOTITLE](/free-pro-team@latest/education/about-github-education). ## Discounts for nonprofits and libraries @@ -38,4 +38,4 @@ If your organization already has a paid plan, your organization's last transacti ## Further reading -* [AUTOTITLE](/billing/managing-your-billing/about-billing-on-github) +* [AUTOTITLE](/billing/get-started/how-billing-works) diff --git a/content/billing/concepts/enterprise-billing/billing-for-enterprises.md b/content/billing/concepts/enterprise-billing/billing-for-enterprises.md index e8f5598162ef..1074a8182506 100644 --- a/content/billing/concepts/enterprise-billing/billing-for-enterprises.md +++ b/content/billing/concepts/enterprise-billing/billing-for-enterprises.md @@ -26,7 +26,7 @@ category: Each member of your enterprise uses a license (previously known as a seat). The bill for your {% data variables.product.prodname_enterprise %} plan is based on the number of licenses consumed by your enterprise. -If you have an enterprise account on {% data variables.product.prodname_ghe_cloud %}, the enterprise account is the central point for all billing within your enterprise, including the organizations that your enterprise owns. Enterprise owners and billing managers can access and manage billing for the enterprise. For more information, see [AUTOTITLE](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise). +If you have an enterprise account on {% data variables.product.prodname_ghe_cloud %}, the enterprise account is the central point for all billing within your enterprise, including the organizations that your enterprise owns. Enterprise owners and billing managers can access and manage billing for the enterprise. For more information, see [AUTOTITLE](/admin/managing-accounts-and-repositories/managing-roles-in-your-enterprise/abilities-of-roles). > [!TIP] > {% ifversion fpt or ghec %} @@ -35,7 +35,7 @@ If you have an enterprise account on {% data variables.product.prodname_ghe_clou > {% data reusables.billing.ghes-with-no-enterprise-account %} > {% endif %} -To learn which people consume a license in your enterprise, see [AUTOTITLE](/billing/reference/license-consumption). +To learn which people consume a license in your enterprise, see [AUTOTITLE](/billing/reference/github-license-users). ## Invoiced customers @@ -51,11 +51,11 @@ There are two billing models for {% data variables.product.prodname_enterprise % {% data reusables.enterprise-licensing.unique-user-licensing-model %} -To ensure the same user isn't consuming more than one license for multiple enterprise deployments, you synchronize license usage between your {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} environments. See [AUTOTITLE](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise). +To ensure the same user isn't consuming more than one license for multiple enterprise deployments, you synchronize license usage between your {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} environments. See [AUTOTITLE](/billing/concepts/enterprise-billing/combined-enterprise-use). ## Further reading -* [AUTOTITLE](/admin/overview/about-enterprise-accounts) -* [AUTOTITLE](/billing/managing-the-plan-for-your-github-account/about-per-user-pricing) +* [AUTOTITLE](/admin/concepts/enterprise-fundamentals/enterprise-accounts) +* [AUTOTITLE](/billing/reference/github-license-users) * [AUTOTITLE](/billing/how-tos/manage-plan-and-licenses/view-enterprise-usage) * [AUTOTITLE](/enterprise-cloud@latest/billing/how-tos/set-up-payment/manage-enterprise-invoice){% ifversion ghes %} in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %} diff --git a/content/billing/concepts/enterprise-billing/combined-enterprise-use.md b/content/billing/concepts/enterprise-billing/combined-enterprise-use.md index adbe2423dea8..312ac020aa51 100644 --- a/content/billing/concepts/enterprise-billing/combined-enterprise-use.md +++ b/content/billing/concepts/enterprise-billing/combined-enterprise-use.md @@ -69,8 +69,8 @@ There are two types of {% data variables.product.prodname_enterprise %} (GHE) li ## Further reading -* [AUTOTITLE](/billing/managing-the-plan-for-your-github-account/about-per-user-pricing) +* [AUTOTITLE](/billing/reference/github-license-users) * [Pricing](https://github.com/pricing) -* [AUTOTITLE](/billing/managing-your-billing/about-billing-for-your-enterprise) +* [AUTOTITLE](/billing/concepts/enterprise-billing/billing-for-enterprises) * [AUTOTITLE]({% ifversion fpt or ghec %}/enterprise-server@latest{% endif %}/admin/installation/setting-up-a-github-enterprise-server-instance) * The [{% data variables.product.prodname_enterprise %} Releases](https://enterprise.github.com/releases/) website diff --git a/content/billing/concepts/enterprise-billing/ghes-license-files.md b/content/billing/concepts/enterprise-billing/ghes-license-files.md index d85527e642a5..4b81b7b06aa6 100644 --- a/content/billing/concepts/enterprise-billing/ghes-license-files.md +++ b/content/billing/concepts/enterprise-billing/ghes-license-files.md @@ -23,7 +23,7 @@ If your license expires, you won't be able to access {% data variables.product.p ## Next steps -* To download your license file, see [AUTOTITLE](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise). -* To upload your license file to {% data variables.product.prodname_ghe_server %}, see {% ifversion fpt or ghec %}[AUTOTITLE](/enterprise-server@latest/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server) in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}[AUTOTITLE](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server).{% endif %} -* To back up your {% data variables.product.prodname_ghe_server %} instance, see {% ifversion fpt or ghec %}[Configuring backups on your appliance](/enterprise-server@latest/admin/guides/installation/configuring-backups-on-your-appliance) in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}[AUTOTITLE](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance).{% endif %} +* To download your license file, see [AUTOTITLE](/billing/how-tos/manage-server-licenses/download-your-license). +* To upload your license file to {% data variables.product.prodname_ghe_server %}, see {% ifversion fpt or ghec %}[AUTOTITLE](/enterprise-server@latest/billing/how-tos/manage-server-licenses/upload-new-license) in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}[AUTOTITLE](/billing/how-tos/manage-server-licenses/upload-new-license).{% endif %} +* To back up your {% data variables.product.prodname_ghe_server %} instance, see {% ifversion fpt or ghec %}[Configuring backups on your appliance](/enterprise-server@latest/admin/backing-up-and-restoring-your-instance/configuring-backups-on-your-instance) in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}[AUTOTITLE](/admin/backing-up-and-restoring-your-instance/configuring-backups-on-your-instance).{% endif %} * If you have questions about renewing your license, contact {% data variables.contact.contact_enterprise_sales %}. diff --git a/content/billing/concepts/enterprise-billing/visual-studio-subs.md b/content/billing/concepts/enterprise-billing/visual-studio-subs.md index eba02000f9be..4d84716aad1f 100644 --- a/content/billing/concepts/enterprise-billing/visual-studio-subs.md +++ b/content/billing/concepts/enterprise-billing/visual-studio-subs.md @@ -27,7 +27,7 @@ category: To use the {% data variables.product.prodname_enterprise %} portion of the license, each subscriber's personal account on {% data variables.product.prodname_dotcom %} must be or become a member of an organization owned by your enterprise on {% data variables.product.prodname_dotcom %}. To accomplish this, organization owners can invite new members to an organization by email address. The subscriber can accept the invitation with an existing personal account or create a new account. -For more information about the setup of {% data variables.visual_studio.prodname_vss_ghe %}, see [AUTOTITLE](/billing/managing-billing-for-your-products/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise). +For more information about the setup of {% data variables.visual_studio.prodname_vss_ghe %}, see [AUTOTITLE](/billing/how-tos/set-up-payment/set-up-vs-subscription). ## About licenses for {% data variables.visual_studio.prodname_vss_ghec %} @@ -47,7 +47,7 @@ For more information about {% data variables.product.prodname_enterprise %}, see For users only on {% data variables.product.prodname_ghe_server %}, each {% data variables.product.prodname_vs %} subscriber will only consume one license as long as the email address associated with their {% data variables.product.prodname_ghe_server %} account matches their {% data variables.product.prodname_vs %} UPN. This does not apply if you have switched to **usage-based billing**, in which case users must also be on {% data variables.product.prodname_ghe_cloud %} to consume a bundled license. -For users on both {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}, only one license will be consumed as long as you follow the instructions in the 'About licenses for {% data variables.visual_studio.prodname_vss_ghec %}' section, and the user's accounts are linked as described in [AUTOTITLE](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud). +For users on both {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}, only one license will be consumed as long as you follow the instructions in the 'About licenses for {% data variables.visual_studio.prodname_vss_ghec %}' section, and the user's accounts are linked as described in [AUTOTITLE](/billing/how-tos/manage-server-licenses/sync-license-usage). ## Further reading diff --git a/content/billing/concepts/impact-of-plan-changes.md b/content/billing/concepts/impact-of-plan-changes.md index 28bc4722c2db..4ab5370e8d79 100644 --- a/content/billing/concepts/impact-of-plan-changes.md +++ b/content/billing/concepts/impact-of-plan-changes.md @@ -38,7 +38,7 @@ Key takeaways: Making a change to the {% data variables.product.github %} plan for your personal account, organization, or enterprise account does not affect billing for use of {% data variables.product.github %} features, such as {% data variables.product.prodname_copilot_short %} or paid apps purchased in {% data variables.product.prodname_marketplace %}. -For more information, see [AUTOTITLE](/get-started/learning-about-github/githubs-plans) and [AUTOTITLE](/billing/using-the-billing-platform/about-billing-on-github). +For more information, see [AUTOTITLE](/get-started/learning-about-github/githubs-plans) and [AUTOTITLE](/billing/get-started/how-billing-works). ## Examples @@ -51,7 +51,7 @@ The following examples illustrate how billing rules are applied in practice: ## Further reading -* [AUTOTITLE](/billing/managing-the-plan-for-your-github-account) -* [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-marketplace-apps) -* [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-git-large-file-storage) -* [AUTOTITLE](/billing/managing-the-plan-for-your-github-account/about-per-user-pricing) +* [AUTOTITLE](/billing/how-tos/manage-plan-and-licenses) +* [AUTOTITLE](/billing/how-tos/pay-third-parties) +* [AUTOTITLE](/billing/how-tos/products) +* [AUTOTITLE](/billing/reference/github-license-users) diff --git a/content/billing/concepts/product-billing/git-lfs.md b/content/billing/concepts/product-billing/git-lfs.md index df45072793aa..3000b68dcc42 100644 --- a/content/billing/concepts/product-billing/git-lfs.md +++ b/content/billing/concepts/product-billing/git-lfs.md @@ -116,7 +116,7 @@ You pay for any additional use above your quota using the payment method set up Bandwidth is billed for each GiB of data downloaded. Storage is billed by calculating an hourly usage rate. * To estimate costs for paid {% data variables.large_files.product_name_short %} usage, use the {% data variables.product.github %} [pricing calculator](https://github.com/pricing/calculator?feature=lfs). -* To view your current storage and bandwidth, see [AUTOTITLE](/billing/managing-billing-for-your-products/viewing-your-product-usage). +* To view your current storage and bandwidth, see [AUTOTITLE](/billing/how-tos/products/view-productlicense-use). ### Example storage cost calculation diff --git a/content/billing/concepts/product-billing/github-actions.md b/content/billing/concepts/product-billing/github-actions.md index 87945780cb5d..70901bfd8990 100644 --- a/content/billing/concepts/product-billing/github-actions.md +++ b/content/billing/concepts/product-billing/github-actions.md @@ -21,7 +21,7 @@ contentType: concepts ## How use of {% data variables.product.prodname_actions %} is measured -{% data variables.product.prodname_actions %} usage is **free** for **self-hosted runners** and for **public repositories** that use standard {% data variables.product.github %}-hosted runners. See [AUTOTITLE](/actions/writing-workflows/choosing-where-your-workflow-runs/choosing-the-runner-for-a-job#standard-github-hosted-runners-for-public-repositories). +{% data variables.product.prodname_actions %} usage is **free** for **self-hosted runners** and for **public repositories** that use standard {% data variables.product.github %}-hosted runners. See [AUTOTITLE](/actions/how-tos/write-workflows/choose-where-workflows-run/choose-the-runner-for-a-job#standard-github-hosted-runners-for-public-repositories). For **private repositories**, each {% data variables.product.github %} account receives a quota of free minutes, artifact storage, and cache storage for use with {% data variables.product.github %}-hosted runners, depending on the account's plan. Any usage beyond the included amounts is billed to your account. @@ -145,7 +145,7 @@ You pay for any additional use above your quota using the payment method set up For {% data variables.product.github %}-hosted runners, storage is billed based on hourly usage of artifacts and caches throughout the month. Minutes are calculated based on the total processing time used by each runner type during the month. * To estimate costs for paid usage, use the {% data variables.product.github %} [pricing calculator](https://github.com/pricing/calculator?feature=actions). -* To view your current costs, see [AUTOTITLE](/billing/managing-billing-for-your-products/viewing-your-product-usage). +* To view your current costs, see [AUTOTITLE](/billing/how-tos/products/view-productlicense-use). > [!NOTE] > The billing dashboard may show your Actions usage as a dollar amount ("spend") rather than raw minutes. This amount already reflects any applicable minute costs. diff --git a/content/billing/concepts/product-billing/github-advanced-security.md b/content/billing/concepts/product-billing/github-advanced-security.md index b25042e88d32..752f23bc68b3 100644 --- a/content/billing/concepts/product-billing/github-advanced-security.md +++ b/content/billing/concepts/product-billing/github-advanced-security.md @@ -35,7 +35,7 @@ For more information, see [feature summary and pricing information](https://gith A subset of {% data variables.product.prodname_AS %} features are available to **all public repositories** on {% data variables.product.prodname_dotcom_the_website %} **free of charge**. If you change the visibility of a public repository to private and don't pay for {% data variables.product.prodname_AS %}, {% data variables.product.prodname_AS %} features will be disabled for that repository. -Use of {% data variables.product.prodname_AS %} features in **all other repositories requires a license**. Your license usage is calculated based on the number of **unique, active committers** to repositories with {% data variables.product.prodname_GH_cs_or_sp %} features enabled. {% data variables.product.prodname_github_app %} bots are ignored. For information about differences between bot and machine accounts, see [AUTOTITLE](/apps/creating-github-apps/setting-up-a-github-app/differences-between-github-apps-and-oauth-apps#machine-vs-bot-accounts). +Use of {% data variables.product.prodname_AS %} features in **all other repositories requires a license**. Your license usage is calculated based on the number of **unique, active committers** to repositories with {% data variables.product.prodname_GH_cs_or_sp %} features enabled. {% data variables.product.prodname_github_app %} bots are ignored. For information about differences between bot and machine accounts, see [AUTOTITLE](/apps/oauth-apps/building-oauth-apps/differences-between-github-apps-and-oauth-apps#machine-vs-bot-accounts). ### Active and unique committers @@ -46,15 +46,15 @@ Each **active committer** to at least one repository with an {% data variables.p > [!NOTE] When a repository is migrated to {% data variables.product.github %} using {% data variables.product.prodname_importer_proper_name %}, {% data variables.product.prodname_GHAS %} only consumes licenses for commits and pushes made _after_ migration. Historic contributions from _before_ the migration are not considered. For more information, see [AUTOTITLE](/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/about-github-enterprise-importer). -You can see the active and unique committers to an organization on the Global settings page for {% data variables.product.UI_advanced_security %}. Under "{% data variables.product.prodname_secret_protection %} repositories" and "{% data variables.product.prodname_code_security %} repositories", summaries and repository-level details are reported. See [AUTOTITLE](/code-security/securing-your-organization/enabling-security-features-in-your-organization/configuring-global-security-settings-for-your-organization). +You can see the active and unique committers to an organization on the Global settings page for {% data variables.product.UI_advanced_security %}. Under "{% data variables.product.prodname_secret_protection %} repositories" and "{% data variables.product.prodname_code_security %} repositories", summaries and repository-level details are reported. See [AUTOTITLE](/code-security/how-tos/secure-at-scale/configure-organization-security/establish-complete-coverage/configure-global-settings). ## Free use of {% data variables.product.prodname_GHAS %} features {% data variables.product.github %} makes some {% data variables.product.prodname_AS %} features available free of charge on {% data variables.product.prodname_dotcom_the_website %}. * **All public repositories** have access to code scanning, secret scanning, and dependency review. -* **{% data variables.product.prodname_secret_risk_assessment_caps %}** is available for organizations on {% data variables.product.prodname_dotcom_the_website %}. See {% ifversion fpt or ghec %}[AUTOTITLE](/code-security/securing-your-organization/understanding-your-organizations-exposure-to-leaked-secrets/viewing-the-secret-risk-assessment-report-for-your-organization){% elsif ghes %}[AUTOTITLE](/enterprise-cloud@latest/code-security/securing-your-organization/understanding-your-organizations-exposure-to-leaked-secrets/viewing-the-secret-risk-assessment-report-for-your-organization) in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}.{% ifversion code-security-risk-assessment %} -* **{% data variables.product.prodname_code_security_risk_assessment_caps %}** is available for organizations on {% data variables.product.prodname_dotcom_the_website %}. See [AUTOTITLE](/code-security/concepts/code-scanning/code-security-risk-assessment).{% endif %} +* **{% data variables.product.prodname_secret_risk_assessment_caps %}** is available for organizations on {% data variables.product.prodname_dotcom_the_website %}. See {% ifversion fpt or ghec %}[AUTOTITLE](/code-security/how-tos/secure-at-scale/configure-organization-security/configure-specific-tools/viewing-your-security-risk-assessment-reports){% elsif ghes %}[AUTOTITLE](/enterprise-cloud@latest/code-security/how-tos/secure-at-scale/configure-organization-security/configure-specific-tools/viewing-your-security-risk-assessment-reports) in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}.{% ifversion code-security-risk-assessment %} +* **{% data variables.product.prodname_code_security_risk_assessment_caps %}** is available for organizations on {% data variables.product.prodname_dotcom_the_website %}. See [AUTOTITLE](/code-security/concepts/code-scanning/risk-assessment).{% endif %} For full details of available features, see [AUTOTITLE](/get-started/learning-about-github/about-github-advanced-security). @@ -85,10 +85,10 @@ There are two different ways to pay for licenses. * **Volume/subscription billing** available for {% data variables.product.prodname_enterprise %} plans only - * Purchase a specific number of {% data variables.product.prodname_GHAS_cs_or_sp %} licenses that last for a defined period, typically at least a year, see {% ifversion fpt or ghec %}[AUTOTITLE](/billing/how-tos/products/add-advanced-security){% elsif ghes %}[AUTOTITLE](/enterprise-cloud@latest/billing/how-tos/products/add-advanced-security) in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}. + * Purchase a specific number of {% data variables.product.prodname_GHAS_cs_or_sp %} licenses that last for a defined period, typically at least a year, see {% ifversion fpt or ghec %}[AUTOTITLE](/billing/how-tos/products/buy-advanced-security){% elsif ghes %}[AUTOTITLE](/enterprise-cloud@latest/billing/how-tos/products/buy-advanced-security) in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}. * If the usage of {% data variables.product.prodname_AS %} by active committers exceeds the number of licenses purchased, you need to purchase additional licenses to cover this overage usage. -To view your current license usage, see [AUTOTITLE](/billing/managing-billing-for-your-products/viewing-your-product-usage). +To view your current license usage, see [AUTOTITLE](/billing/how-tos/products/view-productlicense-use). ### Understanding usage @@ -142,7 +142,7 @@ For more information about budgets, see [AUTOTITLE](/billing/concepts/budgets-an {% data reusables.billing.actions-usage-delay %} -If your enterprise uses {% data variables.product.prodname_AS %} on both {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}, you can ensure users don't consume multiple licenses unnecessarily by synchronizing license usage between environments. See [AUTOTITLE](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud). +If your enterprise uses {% data variables.product.prodname_AS %} on both {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}, you can ensure users don't consume multiple licenses unnecessarily by synchronizing license usage between environments. See [AUTOTITLE](/billing/how-tos/manage-server-licenses/sync-license-usage). ### Volume/subscription billing @@ -150,7 +150,7 @@ Each license specifies a maximum number of accounts that can use {% data variabl As soon as you make licenses available, by disabling {% data variables.product.prodname_GHAS_cs_or_sp %} in some repositories, or by increasing your license size, the options for enabling {% data variables.product.prodname_GHAS_cs_and_sp %} will work again as normal. -You can enforce policies to allow or disallow the use of {% data variables.product.prodname_AS %} by organizations owned by your enterprise account. See [AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise). +You can enforce policies to allow or disallow the use of {% data variables.product.prodname_AS %} by organizations owned by your enterprise account. See [AUTOTITLE](/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise). > [!TIP] > All standalone instances of {% data variables.product.prodname_ghe_server %} use volume/subscription licenses. Contact [{% data variables.product.github %}'s Sales team](https://enterprise.github.com/contact) if you want to make changes to your license. @@ -172,8 +172,7 @@ See [AUTOTITLE](/billing/how-tos/products/disable-ghas-for-enterprise). ## Further reading -* [AUTOTITLE](/code-security/trialing-github-advanced-security/planning-a-trial-of-ghas) -* [AUTOTITLE](/code-security/securing-your-organization/introduction-to-securing-your-organization-at-scale/about-enabling-security-features-at-scale) -* [AUTOTITLE](/admin/managing-code-security/securing-your-enterprise/about-security-configurations) +* [AUTOTITLE](/code-security/tutorials/trialing-github-advanced-security/planning-a-trial-of-ghas) +* [AUTOTITLE](/code-security/concepts/security-at-scale/organization-security) * [AUTOTITLE](/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise) diff --git a/content/billing/concepts/product-billing/github-code-quality.md b/content/billing/concepts/product-billing/github-code-quality.md index 7bca0aa7c530..9db9e1d7e417 100644 --- a/content/billing/concepts/product-billing/github-code-quality.md +++ b/content/billing/concepts/product-billing/github-code-quality.md @@ -42,7 +42,7 @@ To view consumption of actions by the `{% data variables.code-quality.workflow_n When {% data variables.product.prodname_code_quality_short %} is generally available, use of the product will incur three types of costs for an organization: * **{% data variables.product.prodname_actions %} minutes** — {% data variables.product.prodname_code_quality_short %} scans run as {% data variables.product.prodname_actions %} workflows and consume {% data variables.product.prodname_actions %} minutes, unless you use self-hosted runners. For more information, see [AUTOTITLE](/billing/concepts/product-billing/github-actions). * **{% data variables.product.prodname_ai_credits %}** — {% data variables.product.prodname_code_quality_short %} features that use AI models consume {% data variables.product.prodname_ai_credits_short %}. Each interaction is priced based on the number of tokens consumed, where 1 {% data variables.product.prodname_ai_credit_singular %} = {% data variables.product.prodname_ai_credits_value %}. {% data reusables.code-quality.model-usage %} For more information about how {% data variables.product.prodname_ai_credits_short %} work, see [AUTOTITLE](/copilot/concepts/billing/usage-based-billing-for-organizations-and-enterprises). -* **Active committers** — Your license usage is calculated based on the number of unique, active committers to repositories with {% data variables.product.prodname_code_quality_short %} enabled. {% data variables.product.prodname_github_app %} bots are ignored. For information about differences between bot and machine accounts, see [AUTOTITLE](/apps/creating-github-apps/setting-up-a-github-app/differences-between-github-apps-and-oauth-apps#machine-vs-bot-accounts). +* **Active committers** — Your license usage is calculated based on the number of unique, active committers to repositories with {% data variables.product.prodname_code_quality_short %} enabled. {% data variables.product.prodname_github_app %} bots are ignored. For information about differences between bot and machine accounts, see [AUTOTITLE](/apps/oauth-apps/building-oauth-apps/differences-between-github-apps-and-oauth-apps#machine-vs-bot-accounts). #### Active and unique committers @@ -55,6 +55,6 @@ Users can contribute to multiple repositories or organizations. Usage is measure ## Further reading -* [AUTOTITLE](/code-security/code-quality/get-started/quickstart) +* [AUTOTITLE](/code-security/tutorials/improve-code-quality/quickstart) * [AUTOTITLE](/billing/concepts/product-billing/github-actions) * [AUTOTITLE](/copilot/concepts/billing/usage-based-billing-for-organizations-and-enterprises) diff --git a/content/billing/concepts/product-billing/github-codespaces.md b/content/billing/concepts/product-billing/github-codespaces.md index b713f0dd7c23..a2fb8a5f7417 100644 --- a/content/billing/concepts/product-billing/github-codespaces.md +++ b/content/billing/concepts/product-billing/github-codespaces.md @@ -82,7 +82,7 @@ If your account does not have a valid payment method on file, usage is blocked o If you are blocked from resuming a codespace and need to continue work on changes in your codespace, you can do any of the following: -* Add a payment method and review your budget settings to ensure they meet your usage needs. See [AUTOTITLE](/billing/tutorials/set-up-budgets#viewing-budgets). +* Add a payment method and review your budget settings to ensure they meet your usage needs. See [AUTOTITLE](/billing/how-tos/set-up-budgets#viewing-budgets). * Export the changes from the codespace to a branch. See [AUTOTITLE](/codespaces/troubleshooting/exporting-changes-to-a-branch). * Wait for your monthly included usage to reset at the start of the next monthly billing cycle. @@ -91,7 +91,7 @@ If you are blocked from resuming a codespace and need to continue work on change You pay for using {% data variables.product.prodname_codespaces %} using the payment method set up for your {% data variables.product.github %} account. See [AUTOTITLE](/billing/how-tos/set-up-payment/manage-payment-info). * To estimate costs for paid {% data variables.product.prodname_github_codespaces %} usage, use the {% data variables.product.github %} [pricing calculator](https://github.com/pricing/calculator?feature=codespaces). -* To view your current minutes and storage, see [AUTOTITLE](/billing/managing-billing-for-your-products/viewing-your-product-usage). +* To view your current minutes and storage, see [AUTOTITLE](/billing/how-tos/products/view-productlicense-use). * To optimize the use of codespaces: * For personal accounts, see [AUTOTITLE](/codespaces/troubleshooting/troubleshooting-included-usage) * For organization accounts, see [AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization) diff --git a/content/billing/concepts/product-billing/github-copilot-licenses.md b/content/billing/concepts/product-billing/github-copilot-licenses.md index bd27f6c5866c..8caea7c23397 100644 --- a/content/billing/concepts/product-billing/github-copilot-licenses.md +++ b/content/billing/concepts/product-billing/github-copilot-licenses.md @@ -43,7 +43,7 @@ There are several ways to use {% data variables.product.prodname_copilot_short % ### Educational and open source benefits * {% data variables.copilot.copilot_student_short %} offers free access to {% data variables.product.prodname_copilot_short %}'s premium features for verified students. See [AUTOTITLE](/copilot/how-tos/copilot-on-github/set-up-copilot/enable-copilot/set-up-for-students). -* {% data variables.copilot.copilot_pro_short %} is free for verified teachers and maintainers of popular open source projects. See [AUTOTITLE](/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/getting-started-with-copilot-on-your-personal-account/getting-free-access-to-copilot-pro-as-a-student-teacher-or-maintainer). +* {% data variables.copilot.copilot_pro_short %} is free for verified teachers and maintainers of popular open source projects. See [AUTOTITLE](/copilot/how-tos/copilot-on-github/set-up-copilot/enable-copilot/set-up-for-teachers-and-os-maintainers). ## How usage of {% data variables.product.prodname_copilot_short %} licenses is measured @@ -55,7 +55,7 @@ Usage of {% data variables.product.prodname_copilot_short %} licenses is measure * Downgrades take effect at the start of the next billing cycle and are generally not prorated. * Canceling a monthly plan keeps access until the end of the current billing cycle, with no proration. -For details on billing and proration, see [AUTOTITLE](/copilot/concepts/billing/billing-for-individuals). +For details on billing and proration, see [AUTOTITLE](/copilot/concepts/billing/usage-based-billing-for-individuals). ### Organizations and enterprises @@ -93,7 +93,7 @@ To help manage your budget for {% data variables.product.prodname_copilot_short {% data reusables.copilot.plans.ai-cap-recommend-upgrade %} -For more information about using budgets to control spending, see [AUTOTITLE](/billing/managing-your-billing/using-budgets-control-spending). +For more information about using budgets to control spending, see [AUTOTITLE](/billing/how-tos/set-up-budgets). ### Organizations and enterprises diff --git a/content/billing/concepts/product-billing/github-models.md b/content/billing/concepts/product-billing/github-models.md index 1c443ed08f5b..3ee361604354 100644 --- a/content/billing/concepts/product-billing/github-models.md +++ b/content/billing/concepts/product-billing/github-models.md @@ -13,7 +13,7 @@ category: > [!NOTE] > * {% data variables.product.prodname_github_models %} for organizations and repositories is in {% data variables.release-phases.public_preview %} and subject to change. -> * Billing for {% data variables.product.prodname_github_models %} is separate from billing for {% data variables.product.prodname_copilot %}. For more information about how models in {% data variables.product.prodname_copilot %} are billed, see [AUTOTITLE](/billing/managing-billing-for-your-products/about-billing-for-github-copilot). +> * Billing for {% data variables.product.prodname_github_models %} is separate from billing for {% data variables.product.prodname_copilot %}. For more information about how models in {% data variables.product.prodname_copilot %} are billed, see [AUTOTITLE](/billing/concepts/product-billing/github-copilot-licenses). ## How use of {% data variables.product.prodname_github_models %} is measured @@ -25,7 +25,7 @@ The number of model requests and tokens you have used is reset after each billin ### Token units -A token unit is calculated by multiplying the number of input and output tokens by their respective model multipliers. All model usage, regardless of the underlying provider or model, is measured in token units. While some providers display prices per 1,000 or per 1,000,000 tokens, {% data variables.product.prodname_github_models %} standardizes billing to the token unit level. This means you are billed using a single SKU and a unified price per token unit, no matter which supported model you use. See [AUTOTITLE](/billing/reference/models-multipliers-and-costs). +A token unit is calculated by multiplying the number of input and output tokens by their respective model multipliers. All model usage, regardless of the underlying provider or model, is measured in token units. While some providers display prices per 1,000 or per 1,000,000 tokens, {% data variables.product.prodname_github_models %} standardizes billing to the token unit level. This means you are billed using a single SKU and a unified price per token unit, no matter which supported model you use. See [AUTOTITLE](/billing/reference/costs-for-github-models). ### Example calculation @@ -69,7 +69,7 @@ Free usage includes: For full details of rate limits and quotas, see [Rate limits](/github-models/use-github-models/prototyping-with-ai-models#rate-limits). > [!TIP] -> If you use custom models from third-party providers with your own API keys, there is no impact on your bill in {% data variables.product.github %}. See [AUTOTITLE](/github-models/github-models-at-scale/set-up-custom-model-integration-models-byok). +> If you use custom models from third-party providers with your own API keys, there is no impact on your bill in {% data variables.product.github %}. See [AUTOTITLE](/github-models/github-models-at-scale/using-your-own-api-keys-in-github-models). ## Using more than your included quota @@ -93,13 +93,13 @@ You pay for additional use of {% data variables.product.prodname_github_models % {% data variables.product.prodname_github_models %} pricing is based on the number of token units used, at a fixed price of $0.00001 USD per token unit. -At the end of your billing cycle, {% data variables.product.github %} calculates the cost of token units used, starting from your first request after opting in to paid usage. See [AUTOTITLE](/billing/managing-billing-for-your-products/viewing-your-product-usage). +At the end of your billing cycle, {% data variables.product.github %} calculates the cost of token units used, starting from your first request after opting in to paid usage. See [AUTOTITLE](/billing/how-tos/products/view-productlicense-use). {% data variables.product.prodname_github_models %} usage can be paid for by one or more of the following methods: * For enterprises, organizations, or personal accounts directly billed by {% data variables.product.github %}, the billing of {% data variables.product.prodname_github_models %} is based on your metered usage for each billing period, and pricing varies by the number of model requests, tokens, and the model multiplier. * For invoiced accounts, contact {% data variables.contact.contact_enterprise_sales %} to discuss billing for {% data variables.product.prodname_github_models %} usage. -* Accounts with an existing Azure subscription can use that subscription to pay for model inference by bringing their own API key for custom models. In this case, billing is based on the model provider’s pricing and is managed through the Azure subscription. See [AUTOTITLE](/github-models/github-models-at-scale/set-up-custom-model-integration-models-byok). +* Accounts with an existing Azure subscription can use that subscription to pay for model inference by bringing their own API key for custom models. In this case, billing is based on the model provider’s pricing and is managed through the Azure subscription. See [AUTOTITLE](/github-models/github-models-at-scale/using-your-own-api-keys-in-github-models). You are considered to be directly billed by {% data variables.product.github %} if you pay for {% data variables.product.github %} using a credit card, PayPal, or by invoice. @@ -111,7 +111,7 @@ Enterprises and organizations can opt in to paid usage to access expanded model Enterprises, organizations and personal accounts may have default budgets to limit spending. Check the budgets for your account to ensure they are appropriate for your usage needs. -For more information, see [AUTOTITLE](/billing/managing-your-billing/using-budgets-control-spending). +For more information, see [AUTOTITLE](/billing/how-tos/set-up-budgets). ## Further reading diff --git a/content/billing/concepts/product-billing/github-packages.md b/content/billing/concepts/product-billing/github-packages.md index cef0601d3e38..f9b90cb9ac4e 100644 --- a/content/billing/concepts/product-billing/github-packages.md +++ b/content/billing/concepts/product-billing/github-packages.md @@ -87,7 +87,7 @@ You pay for any additional use above your quota using the payment method set up Data transfer is billed for each GB of data transferred. Storage is billed by calculating an hourly usage rate. * {% data reusables.dotcom_billing.pricing_calculator.pricing_cal_packages %} -* To view your current storage and bandwidth, see [AUTOTITLE](/billing/managing-billing-for-your-products/viewing-your-product-usage). +* To view your current storage and bandwidth, see [AUTOTITLE](/billing/how-tos/products/view-productlicense-use). ### Example of how usage is calculated over a month diff --git a/content/billing/concepts/product-billing/github-spark.md b/content/billing/concepts/product-billing/github-spark.md index 1cb1184c8e60..835ac506a734 100644 --- a/content/billing/concepts/product-billing/github-spark.md +++ b/content/billing/concepts/product-billing/github-spark.md @@ -30,7 +30,7 @@ You now have more granular options for managing {% data variables.product.prodna * **Bundled budget**: Combine {% data variables.product.prodname_spark_short %} {% data variables.product.prodname_ai_credits_short %} with other {% data variables.product.prodname_copilot_short %} costs in a single budget for simplified management. * **Individual product budget**: Set a dedicated budget specifically for {% data variables.product.prodname_spark_short %} for granular cost control. -For detailed information about setting up budgets, see [AUTOTITLE](/billing/tutorials/set-up-budgets). +For detailed information about setting up budgets, see [AUTOTITLE](/billing/how-tos/set-up-budgets). ### Analytics and monitoring @@ -53,5 +53,5 @@ In the future, a new billing system will allow sparks to continue being deployed ## Further reading -* [AUTOTITLE](/copilot/responsible-use-of-github-copilot-features/responsible-use-of-github-spark) -* [AUTOTITLE](/copilot/tutorials/building-ai-app-prototypes) +* [AUTOTITLE](/copilot/responsible-use/agents) +* [AUTOTITLE](/copilot/tutorials/spark/build-apps-with-spark) diff --git a/content/billing/concepts/third-party-payments/github-marketplace-apps.md b/content/billing/concepts/third-party-payments/github-marketplace-apps.md index 51179228b674..c8358d27a8f0 100644 --- a/content/billing/concepts/third-party-payments/github-marketplace-apps.md +++ b/content/billing/concepts/third-party-payments/github-marketplace-apps.md @@ -56,13 +56,13 @@ All paid {% data variables.product.prodname_marketplace %} app subscriptions for ## Unit plan limits -For plans that charge per unit (for example, per user), exceeding the purchased units can lead the developer to restrict or disable app access until you move to a plan that covers the higher usage. For more information, see [AUTOTITLE](/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app). +For plans that charge per unit (for example, per user), exceeding the purchased units can lead the developer to restrict or disable app access until you move to a plan that covers the higher usage. For more information, see [AUTOTITLE](/billing/how-tos/pay-third-parties/upgrade-marketplace-app). ## Plan changes and cancellation * **Upgrading or adding capacity** takes effect immediately; a prorated amount may be charged for the rest of the cycle (if applicable). * **Downgrading a paid plan or canceling a paid app** takes effect at the end of the current billing cycle; access continues until then. Your subscription will be moved to your new plan on your next billing date. - To learn how to downgrade a paid plan or cancel a paid app, see [AUTOTITLE](/billing/how-tos/pay-third-parties/downgrade-marketplace-app) and [AUTOTITLE](/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app). + To learn how to downgrade a paid plan or cancel a paid app, see [AUTOTITLE](/billing/how-tos/pay-third-parties/downgrade-marketplace-app) and [AUTOTITLE](/billing/how-tos/pay-third-parties/cancel-marketplace-app). * **Cancelling a free plan** ends the subscription immediately with loss of access. * **Canceling a free trial** on a paid plan ends the trial immediately and access stops. diff --git a/content/billing/get-started/billing-manager-onboard.md b/content/billing/get-started/billing-manager-onboard.md index 9a41f4a9ed13..55aa03726240 100644 --- a/content/billing/get-started/billing-manager-onboard.md +++ b/content/billing/get-started/billing-manager-onboard.md @@ -43,14 +43,14 @@ Now that you understand the basics, you can start monitoring usage and tracking With insight into your spending patterns, you can take proactive steps to manage costs and prevent budget overruns. * Learn how budgets and alerts allow you to track and control spending. See [AUTOTITLE](/billing/concepts/budgets-and-alerts). -* Set up budgets and alerts to proactively address potential overspending before it becomes a problem. See [AUTOTITLE](/billing/tutorials/set-up-budgets). +* Set up budgets and alerts to proactively address potential overspending before it becomes a problem. See [AUTOTITLE](/billing/how-tos/set-up-budgets). * Adjust budgets and thresholds as your organization grows or usage patterns change. ## 4. Attribute costs (enterprise only) If you manage an enterprise account, you can use cost centers to organize and track spending across different teams and business units. -* Organize spend with cost centers to help you see which teams, projects, or business units are responsible for portions of your {% data variables.product.github %} bill. See [AUTOTITLE](/billing/tutorials/use-cost-centers). +* Organize spend with cost centers to help you see which teams, projects, or business units are responsible for portions of your {% data variables.product.github %} bill. See [AUTOTITLE](/billing/how-tos/products/use-cost-centers). * Attribute parts of the bill to specific teams to increase visibility and accountability. * Compare groups and identify opportunities for optimization. @@ -66,5 +66,5 @@ As a billing manager, you'll need to work closely with other stakeholders to sha Now that you understand how billing works on {% data variables.product.github %}, you can look at tutorials to learn how to perform specific tasks. -* To estimate your spending and make informed decisions towards optimal budgeting, see [AUTOTITLE](/billing/tutorials/estimate-spending). +* To estimate your spending and make informed decisions towards optimal budgeting, see [AUTOTITLE](/billing/how-tos/products/estimate-spending). * To find which teams or members drive most of your usage and who's using what, see [AUTOTITLE](/billing/tutorials/gather-insights). diff --git a/content/billing/get-started/how-billing-works.md b/content/billing/get-started/how-billing-works.md index bbab85b2a113..1e3849b7f8b9 100644 --- a/content/billing/get-started/how-billing-works.md +++ b/content/billing/get-started/how-billing-works.md @@ -43,7 +43,7 @@ You can use {% data variables.product.github %} without incurring any costs. If * **Metered usage**: Variable costs that depend on how much you use certain features above the amounts included with your {% data variables.product.github %} plan (for example: {% data variables.product.prodname_actions %}). For more information see, [AUTOTITLE](/billing/reference/product-usage-included) and [AUTOTITLE](/billing/concepts/budgets-and-alerts). > [!TIP] -> {% data variables.product.github %} has discounted plans for verified students and academic faculties, and for non-profit organizations. For more information, see [AUTOTITLE](/billing/managing-the-plan-for-your-github-account/discounted-plans-for-github-accounts). +> {% data variables.product.github %} has discounted plans for verified students and academic faculties, and for non-profit organizations. For more information, see [AUTOTITLE](/billing/concepts/discounted-plans). ## How does billing work? @@ -76,11 +76,11 @@ If the authorization is unsuccessful, the chosen service will not be activated a ## How do I see what I'm billed for? -You can see the billing and usage information for your account at anytime in the "Billing and licensing" pages of your account or using the REST API. For more information, see [AUTOTITLE](/billing/how-tos/products/view-product-use). +You can see the billing and usage information for your account at anytime in the "Billing and licensing" pages of your account or using the REST API. For more information, see [AUTOTITLE](/billing/how-tos/products/view-productlicense-use). ## Next steps * [AUTOTITLE](/get-started/learning-about-github/types-of-github-accounts) -* [AUTOTITLE](/billing/managing-your-billing/managing-your-payment-and-billing-information) -* [AUTOTITLE](/billing/tutorials/set-up-budgets) +* [AUTOTITLE](/billing/how-tos/set-up-payment/manage-payment-info) +* [AUTOTITLE](/billing/how-tos/set-up-budgets) * [AUTOTITLE](/billing/how-tos/set-up-payment/add-sales-tax-certificate) diff --git a/content/billing/get-started/introduction-to-billing.md b/content/billing/get-started/introduction-to-billing.md index e3bf0b7b77b3..3806b1a82efb 100644 --- a/content/billing/get-started/introduction-to-billing.md +++ b/content/billing/get-started/introduction-to-billing.md @@ -49,14 +49,14 @@ If you have questions, please contact {% data variables.contact.contact_support_ You can use the REST API to download the usage report for a personal or organization account. First you will need to create a fine-grained access token with the permissions defined by the end point, see: -* [Get billing usage report for a user](/rest/billing/enhanced-billing?apiVersion=2022-11-28#get-billing-usage-report-for-a-user) -* [Get billing usage report for an organization](/rest/billing/enhanced-billing?apiVersion=2022-11-28#get-billing-usage-report-for-an-organization) -* [Get billing usage report for an enterprise](/rest/enterprise-admin/billing?apiVersion=2022-11-28#get-billing-usage-report-for-an-enterprise) +* [Get billing usage report for a user](/rest/billing/usage?apiVersion=2022-11-28#get-billing-usage-report-for-a-user) +* [Get billing usage report for an organization](/rest/billing/usage?apiVersion=2022-11-28#get-billing-usage-report-for-an-organization) +* [Get billing usage report for an enterprise](/rest/billing/usage?apiVersion=2022-11-28#get-billing-usage-report-for-an-enterprise) -For more information, see [AUTOTITLE](/enterprise-cloud@latest/billing/managing-your-billing/automating-usage-reporting). +For more information, see [AUTOTITLE](/enterprise-cloud@latest/billing/tutorials/automate-usage-reporting). ## Next steps -* [AUTOTITLE](/billing/how-tos/products/view-product-use) -* [AUTOTITLE](/billing/tutorials/set-up-budgets) +* [AUTOTITLE](/billing/how-tos/products/view-productlicense-use) +* [AUTOTITLE](/billing/how-tos/set-up-budgets) * [AUTOTITLE](/billing/tutorials/control-costs-at-scale) diff --git a/content/billing/how-tos/manage-for-client/create-as-csp-partner.md b/content/billing/how-tos/manage-for-client/create-as-csp-partner.md index 0d296a845ac6..6b5ab6dc2fb9 100644 --- a/content/billing/how-tos/manage-for-client/create-as-csp-partner.md +++ b/content/billing/how-tos/manage-for-client/create-as-csp-partner.md @@ -21,7 +21,7 @@ Before you start, make sure you know: * Enterprise name your client would like to use * Email address for receipts * Number of seats your client needs in the enterprise -* Enterprise account type required by your client, see [AUTOTITLE](/admin/managing-iam/understanding-iam-for-enterprises/choosing-an-enterprise-type-for-github-enterprise-cloud) +* Enterprise account type required by your client, see [AUTOTITLE](/enterprise-onboarding/getting-started-with-your-enterprise/choose-an-enterprise-type) ## Step 1: Create the enterprise account in the Azure portal @@ -30,7 +30,7 @@ As a Microsoft CSP partner, you can get started with {% data variables.product.p 1. Sign in to the Microsoft Azure portal. 1. In the search bar, type "{% data variables.product.prodname_dotcom %}" and select **{% data variables.product.prodname_dotcom %}** to go the landing page. 1. Select **Get started with {% data variables.product.prodname_enterprise %}**. -1. Choose an enterprise type. To help you decide which choice is best for the enterprise, see [AUTOTITLE](/admin/identity-and-access-management/understanding-iam-for-enterprises/choosing-an-enterprise-type-for-github-enterprise-cloud). +1. Choose an enterprise type. To help you decide which choice is best for the enterprise, see [AUTOTITLE](/enterprise-onboarding/getting-started-with-your-enterprise/choose-an-enterprise-type). 1. Complete the form with your client's information. {% data reusables.billing.enterprise-create-button %} @@ -53,7 +53,7 @@ At any time during the trial, you can purchase {% data variables.product.prodnam ## Step 3: Invite your client as an enterprise owner -Invite your client to become an enterprise owner. See [AUTOTITLE](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise#inviting-an-enterprise-administrator-to-your-enterprise-account). +Invite your client to become an enterprise owner. See [AUTOTITLE](/enterprise-cloud@latest/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise#inviting-an-enterprise-administrator-to-your-enterprise-account). ## Step 4: Change your role to billing manager diff --git a/content/billing/how-tos/manage-for-client/create-client-enterprise.md b/content/billing/how-tos/manage-for-client/create-client-enterprise.md index 82f7b20ae357..8b91a96ea18c 100644 --- a/content/billing/how-tos/manage-for-client/create-client-enterprise.md +++ b/content/billing/how-tos/manage-for-client/create-client-enterprise.md @@ -21,7 +21,7 @@ Before you start, make sure you know: * Enterprise name your client would like to use * Email address for receipts * Number of seats your client needs in the enterprise -* Enterprise account type required by your client, see [AUTOTITLE](/admin/managing-iam/understanding-iam-for-enterprises/choosing-an-enterprise-type-for-github-enterprise-cloud) +* Enterprise account type required by your client, see [AUTOTITLE](/enterprise-onboarding/getting-started-with-your-enterprise/choose-an-enterprise-type) ## Step 1: Create your personal account on {% data variables.product.prodname_dotcom %} @@ -55,7 +55,7 @@ If you already have a personal account on {% data variables.product.prodname_dot ## Step 4: Invite your client as an enterprise owner -Invite your client to become an enterprise owner. For more information, see [AUTOTITLE](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise#inviting-an-enterprise-administrator-to-your-enterprise-account). +Invite your client to become an enterprise owner. For more information, see [AUTOTITLE](/enterprise-cloud@latest/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise#inviting-an-enterprise-administrator-to-your-enterprise-account). ## Step 5: Change your role to billing manager diff --git a/content/billing/how-tos/manage-plan-and-licenses/downgrade-plan.md b/content/billing/how-tos/manage-plan-and-licenses/downgrade-plan.md index 742bc03820b6..23eeb495c194 100644 --- a/content/billing/how-tos/manage-plan-and-licenses/downgrade-plan.md +++ b/content/billing/how-tos/manage-plan-and-licenses/downgrade-plan.md @@ -44,12 +44,12 @@ If you published a {% data variables.product.prodname_pages %} site in a private {% data reusables.dotcom_billing.org-billing-perms %} -After an organization's plan is downgraded, the organization will lose access to any functionality that is not included in the new plan. If an advanced feature, such as {% data variables.product.prodname_pages %}, is not available for private repositories in your new plan, consider whether you'd like to retain access to the feature by making affected repositories public. For more information, see [Setting repository visibility](/articles/setting-repository-visibility). +After an organization's plan is downgraded, the organization will lose access to any functionality that is not included in the new plan. If an advanced feature, such as {% data variables.product.prodname_pages %}, is not available for private repositories in your new plan, consider whether you'd like to retain access to the feature by making affected repositories public. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility). Downgrading from {% data variables.product.prodname_ghe_cloud %} disables any SAML settings. If you later purchase {% data variables.product.prodname_enterprise %}, you will need to reconfigure SAML. > [!NOTE] -> If your organization is owned by an enterprise account, billing cannot be managed at the organization level. To downgrade, you must remove the organization from the enterprise account first. For more information, see [AUTOTITLE](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise). +> If your organization is owned by an enterprise account, billing cannot be managed at the organization level. To downgrade, you must remove the organization from the enterprise account first. For more information, see [AUTOTITLE](/enterprise-cloud@latest/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise). {% data reusables.organizations.billing-settings %} 1. Under "Current plan", use the **Edit** drop-down and click the downgrade option you want. @@ -60,7 +60,7 @@ Downgrading from {% data variables.product.prodname_ghe_cloud %} disables any SA {% data reusables.dotcom_billing.org-billing-perms %} -{% data reusables.dotcom_billing.switch-legacy-billing %} For more information, see [AUTOTITLE](/billing/managing-the-plan-for-your-github-account/upgrading-your-accounts-plan#switching-your-organization-from-per-repository-to-per-user-pricing). +{% data reusables.dotcom_billing.switch-legacy-billing %} For more information, see [AUTOTITLE](/billing/how-tos/manage-plan-and-licenses/upgrade-plan#switching-your-organization-from-per-repository-to-per-user-pricing). {% data reusables.organizations.billing-settings %} 5. Under "Subscriptions", next to your current plan, select the **Edit** dropdown menu and click **Edit plan**. @@ -75,7 +75,7 @@ If you want to stop paying for {% data variables.product.prodname_enterprise %} If you have a self-serve enterprise account, an enterprise account owner can: -1. Remove or delete all organizations from the enterprise. Removing an organization from an enterprise automatically downgrades the organization to {% data variables.product.prodname_free_team %}. See [AUTOTITLE](/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise). +1. Remove or delete all organizations from the enterprise. Removing an organization from an enterprise automatically downgrades the organization to {% data variables.product.prodname_free_team %}. See [AUTOTITLE](/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise). 1. Review and remove any remaining unaffiliated members from the enterprise. Depending on your policy settings, members who don't belong to any organizations may remain in your enterprise as unaffiliated members. To fully close the account, remove these unaffiliated members. 1. Delete the enterprise account to cancel the {% data variables.product.prodname_enterprise %} subscription. See [AUTOTITLE](/admin/managing-your-enterprise-account/deleting-an-enterprise-account). @@ -83,6 +83,6 @@ If you have a self-serve enterprise account, an enterprise account owner can: * [AUTOTITLE](/billing/how-tos/manage-plan-and-licenses/manage-user-licenses) * [AUTOTITLE](/get-started/learning-about-github/githubs-plans) -* [AUTOTITLE](/billing/managing-the-plan-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process) -* [AUTOTITLE](/billing/managing-your-billing/about-billing-on-github). -* [AUTOTITLE](/billing/managing-the-plan-for-your-github-account/about-per-user-pricing) +* [AUTOTITLE](/billing/concepts/impact-of-plan-changes) +* [AUTOTITLE](/billing/get-started/how-billing-works). +* [AUTOTITLE](/billing/reference/github-license-users) diff --git a/content/billing/how-tos/manage-plan-and-licenses/upgrade-plan.md b/content/billing/how-tos/manage-plan-and-licenses/upgrade-plan.md index 024853a1adfa..a4d3e87d06b8 100644 --- a/content/billing/how-tos/manage-plan-and-licenses/upgrade-plan.md +++ b/content/billing/how-tos/manage-plan-and-licenses/upgrade-plan.md @@ -65,7 +65,7 @@ Upgrading an organization does not affect your personal account or repositories ### Next steps for organizations using {% data variables.product.prodname_ghe_cloud %} -As part of your upgrade to {% data variables.product.prodname_ghe_cloud %}, you set up an enterprise account. An enterprise account allows you to manage multiple organizations. Optionally, you can set up identity and access management for an individual organization or enterprise account. See [AUTOTITLE](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts) and [AUTOTITLE](/enterprise-cloud@latest/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#authentication-through-githubcom-with-additional-saml-access-restriction){% ifversion fpt %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %} +As part of your upgrade to {% data variables.product.prodname_ghe_cloud %}, you set up an enterprise account. An enterprise account allows you to manage multiple organizations. Optionally, you can set up identity and access management for an individual organization or enterprise account. See [AUTOTITLE](/enterprise-cloud@latest/admin/concepts/enterprise-fundamentals/enterprise-accounts) and [AUTOTITLE](/enterprise-cloud@latest/admin/concepts/identity-and-access-management/identity-and-access-management-fundamentals#authentication-through-githubcom-with-additional-saml-access-restriction){% ifversion fpt %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %} {% data reusables.enterprise.create-an-enterprise-account %} See [AUTOTITLE](/enterprise-cloud@latest/admin/managing-your-enterprise-account/creating-an-enterprise-account){% ifversion fpt %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %} @@ -77,7 +77,7 @@ As part of your upgrade to {% data variables.product.prodname_ghe_cloud %}, you ## Switching your organization from per-repository to per-user pricing -{% data reusables.dotcom_billing.switch-legacy-billing %} See [AUTOTITLE](/billing/managing-the-plan-for-your-github-account/about-per-user-pricing). +{% data reusables.dotcom_billing.switch-legacy-billing %} See [AUTOTITLE](/billing/reference/github-license-users). {% data reusables.organizations.billing-settings %} 1. To the right of your plan name, select the **Edit** dropdown menu, then click **Edit plan**. @@ -91,5 +91,5 @@ As part of your upgrade to {% data variables.product.prodname_ghe_cloud %}, you * [AUTOTITLE](/billing/how-tos/manage-plan-and-licenses/manage-user-licenses) * [AUTOTITLE](/get-started/learning-about-github/githubs-plans) -* [AUTOTITLE](/billing/managing-the-plan-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process) -* [AUTOTITLE](/billing/managing-your-billing/about-billing-on-github) +* [AUTOTITLE](/billing/concepts/impact-of-plan-changes) +* [AUTOTITLE](/billing/get-started/how-billing-works) diff --git a/content/billing/how-tos/manage-plan-and-licenses/view-enterprise-usage.md b/content/billing/how-tos/manage-plan-and-licenses/view-enterprise-usage.md index 1128a5c9ae6d..db8f2fd09e25 100644 --- a/content/billing/how-tos/manage-plan-and-licenses/view-enterprise-usage.md +++ b/content/billing/how-tos/manage-plan-and-licenses/view-enterprise-usage.md @@ -33,7 +33,7 @@ The information displayed varies according to your enterprise set up. * {% data variables.product.prodname_ghe_cloud %}, potentially with licenses synchronized from {% data variables.product.prodname_ghe_server %} * {% data variables.product.prodname_ghe_server %} -To learn more about the license data associated with your enterprise account and how the number of consumed user licenses is calculated, see [AUTOTITLE](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise). +To learn more about the license data associated with your enterprise account and how the number of consumed user licenses is calculated, see [AUTOTITLE](/billing/how-tos/troubleshooting/enterprise-license-usage). ## Finding information on {% data variables.product.prodname_ghe_cloud %} @@ -71,7 +71,7 @@ The date of the last license sync occurred is shown under "Enterprise Server ins * "{% data variables.product.prodname_github_connect %} server usage synced" indicates license usage between environments was automatically updated. * "{% data variables.product.prodname_github_connect %} server usage never synced" indicates that {% data variables.product.prodname_github_connect %} is configured, but license usage between environments has never updated successfully. -For more information, see [AUTOTITLE](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud). +For more information, see [AUTOTITLE](/billing/how-tos/manage-server-licenses/sync-license-usage). ### Synchronization of {% data variables.visual_studio.prodname_vss_ghe %} subscriptions @@ -89,4 +89,4 @@ If your {% data variables.product.github %} license includes {% data variables.v ## Reporting license information using the REST API -You can also use the REST API to return consumed licenses data and the status of the license sync job. See [AUTOTITLE](/rest/enterprise-admin/license). +You can also use the REST API to return consumed licenses data and the status of the license sync job. See [AUTOTITLE](/rest/enterprise-admin/licensing). diff --git a/content/billing/how-tos/manage-server-licenses/download-your-license.md b/content/billing/how-tos/manage-server-licenses/download-your-license.md index b12d6867739c..50b4042f3f66 100644 --- a/content/billing/how-tos/manage-server-licenses/download-your-license.md +++ b/content/billing/how-tos/manage-server-licenses/download-your-license.md @@ -42,7 +42,7 @@ There are two possible ways to download a license file for {% data variables.pro 1. If you are an existing {% data variables.product.prodname_enterprise %} customer with an enterprise account on {% data variables.product.prodname_ghe_cloud %}, or if you have {% data variables.enterprise.data_residency_site %} with metered license billing, you can download your license file from {% data variables.product.prodname_dotcom_the_website %} or {% data variables.enterprise.data_residency_site %} using the following instructions. -If you have any questions about downloading your license, contact {% data variables.contact.contact_enterprise_sales %}. For more information about enterprise accounts, see [AUTOTITLE](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion ghes %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% elsif ghec %}.{% endif %} +If you have any questions about downloading your license, contact {% data variables.contact.contact_enterprise_sales %}. For more information about enterprise accounts, see [AUTOTITLE](/enterprise-cloud@latest/admin/concepts/enterprise-fundamentals/enterprise-accounts){% ifversion ghes %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% elsif ghec %}.{% endif %} {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} {% data reusables.enterprise-accounts.licensing-tab-both-platforms %} @@ -55,4 +55,4 @@ If you have any questions about downloading your license, contact {% data variab 1. Scroll down to "Enterprise Server licenses". Next to the license you want to download, click **{% octicon "download" aria-hidden="true" aria-label="download" %} Download**. -After you download your license file, you can upload the file to {% data variables.product.prodname_ghe_server %} to validate your application. For more information, see {% ifversion ghec %}[AUTOTITLE](/enterprise-server@latest/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server) in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}[AUTOTITLE](/enterprise-server@latest/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server).{% endif %} +After you download your license file, you can upload the file to {% data variables.product.prodname_ghe_server %} to validate your application. For more information, see {% ifversion ghec %}[AUTOTITLE](/enterprise-server@latest/billing/how-tos/manage-server-licenses/upload-new-license) in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}[AUTOTITLE](/enterprise-server@latest/billing/how-tos/manage-server-licenses/upload-new-license).{% endif %} diff --git a/content/billing/how-tos/manage-server-licenses/sync-license-usage.md b/content/billing/how-tos/manage-server-licenses/sync-license-usage.md index d9648b381ac5..8344aace1cb2 100644 --- a/content/billing/how-tos/manage-server-licenses/sync-license-usage.md +++ b/content/billing/how-tos/manage-server-licenses/sync-license-usage.md @@ -62,4 +62,4 @@ You can download a JSON file from {% data variables.product.prodname_ghe_server {% data reusables.enterprise-licensing.view-consumed-licenses %} -To make troubleshooting easier, if you synchronize license usage and do not use {% data variables.product.prodname_emus %}, we highly recommend enabling verified domains for your enterprise account on {% data variables.product.prodname_ghe_cloud %}. See [AUTOTITLE](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise){% ifversion ghes %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %} +To make troubleshooting easier, if you synchronize license usage and do not use {% data variables.product.prodname_emus %}, we highly recommend enabling verified domains for your enterprise account on {% data variables.product.prodname_ghe_cloud %}. See [AUTOTITLE](/enterprise-cloud@latest/admin/configuring-settings/configuring-user-applications-for-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise){% ifversion ghes %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %} diff --git a/content/billing/how-tos/manage-server-licenses/upload-new-license.md b/content/billing/how-tos/manage-server-licenses/upload-new-license.md index b55fa606e9c4..bf175d846e96 100644 --- a/content/billing/how-tos/manage-server-licenses/upload-new-license.md +++ b/content/billing/how-tos/manage-server-licenses/upload-new-license.md @@ -16,7 +16,7 @@ category: When you purchase or download a new license for {% data variables.product.prodname_ghe_server %} you must upload the new license file to {% data variables.product.prodname_ghe_server %} to unlock your new user licenses. -If you use {% data variables.product.prodname_ghe_cloud %}, you can download a license from your enterprise. For more information, see [AUTOTITLE](/billing/concepts/enterprise-billing/ghes-license-files) and [AUTOTITLE](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise). +If you use {% data variables.product.prodname_ghe_cloud %}, you can download a license from your enterprise. For more information, see [AUTOTITLE](/billing/concepts/enterprise-billing/ghes-license-files) and [AUTOTITLE](/billing/how-tos/manage-server-licenses/download-your-license). {% data reusables.enterprise-licensing.contact-sales-for-renewals-or-seats %} diff --git a/content/billing/how-tos/pay-third-parties/cancel-marketplace-app.md b/content/billing/how-tos/pay-third-parties/cancel-marketplace-app.md index 94fb41a3df39..ff4419fbfd08 100644 --- a/content/billing/how-tos/pay-third-parties/cancel-marketplace-app.md +++ b/content/billing/how-tos/pay-third-parties/cancel-marketplace-app.md @@ -20,7 +20,7 @@ category: {% ifversion fpt %}{% data reusables.marketplace.marketplace-app-page %}{% endif %} -**When you cancel a paid app, your access and subscription will end on your next billing date. If you cancel during a free trial, you will lose access immediately**. For more information, see [AUTOTITLE](/billing/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace). +**When you cancel a paid app, your access and subscription will end on your next billing date. If you cancel during a free trial, you will lose access immediately**. For more information, see [AUTOTITLE](/billing/concepts/third-party-payments/github-marketplace-apps). {% data reusables.marketplace.downgrade-marketplace-only %} diff --git a/content/billing/how-tos/pay-third-parties/downgrade-marketplace-app.md b/content/billing/how-tos/pay-third-parties/downgrade-marketplace-app.md index 18928b092fe1..1826e473e97f 100644 --- a/content/billing/how-tos/pay-third-parties/downgrade-marketplace-app.md +++ b/content/billing/how-tos/pay-third-parties/downgrade-marketplace-app.md @@ -20,7 +20,7 @@ category: {% ifversion fpt %}{% data reusables.marketplace.marketplace-app-page %}{% endif %} -**When you downgrade an app, your subscription remains active until the end of your current billing cycle. The downgrade takes effect on your next billing date**. For more information, see [AUTOTITLE](/billing/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace). +**When you downgrade an app, your subscription remains active until the end of your current billing cycle. The downgrade takes effect on your next billing date**. For more information, see [AUTOTITLE](/billing/concepts/third-party-payments/github-marketplace-apps). {% data reusables.marketplace.downgrade-marketplace-only %} @@ -58,4 +58,4 @@ category: ## Further reading -* [AUTOTITLE](/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app) +* [AUTOTITLE](/billing/how-tos/pay-third-parties/cancel-marketplace-app) diff --git a/content/billing/how-tos/pay-third-parties/end-sponsorship.md b/content/billing/how-tos/pay-third-parties/end-sponsorship.md index 13ebe1cf9427..e0111c2e27f5 100644 --- a/content/billing/how-tos/pay-third-parties/end-sponsorship.md +++ b/content/billing/how-tos/pay-third-parties/end-sponsorship.md @@ -15,7 +15,7 @@ category: You can set an end date to your sponsorship. The end date assigned will be the last date for which you will be charged for that sponsorship, but the sponsorship will show active for another month. -For example, if July 2025 is set as the end date, the last sponsorship will be charged in July 2025, but the sponsorship will be shown as active until August 2025. For more information about setting an end date to a new sponsorship, see [AUTOTITLE](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor). +For example, if July 2025 is set as the end date, the last sponsorship will be charged in July 2025, but the sponsorship will be shown as active until August 2025. For more information about setting an end date to a new sponsorship, see [AUTOTITLE](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor-through-github). ## Setting an end date for an existing sponsorship diff --git a/content/billing/how-tos/pay-third-parties/upgrade-marketplace-app.md b/content/billing/how-tos/pay-third-parties/upgrade-marketplace-app.md index ea66385f0bf4..f46809a1f20c 100644 --- a/content/billing/how-tos/pay-third-parties/upgrade-marketplace-app.md +++ b/content/billing/how-tos/pay-third-parties/upgrade-marketplace-app.md @@ -20,7 +20,7 @@ category: {% ifversion fpt %}{% data reusables.marketplace.marketplace-app-page %}{% endif %} -**When you upgrade an app, your payment method is charged a prorated amount based on the time remaining until your next billing date**. For more information, see [AUTOTITLE](/billing/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace). +**When you upgrade an app, your payment method is charged a prorated amount based on the time remaining until your next billing date**. For more information, see [AUTOTITLE](/billing/concepts/third-party-payments/github-marketplace-apps). ## Upgrading an app for your personal account diff --git a/content/billing/how-tos/products/buy-advanced-security.md b/content/billing/how-tos/products/buy-advanced-security.md index 90382fce7f9a..4dd0fd729b75 100644 --- a/content/billing/how-tos/products/buy-advanced-security.md +++ b/content/billing/how-tos/products/buy-advanced-security.md @@ -29,7 +29,7 @@ Your current plan is shown with any options to upgrade to a different plan. If your organization or enterprise uses metered billing, then you are ready to start enabling {% data variables.product.prodname_GH_cs_and_sp %}. Whenever you enable a feature or apply a configuration, a modal dialog shows detailed information with estimated billing changes. You can confirm your change or return to the page without making changes. -The most effective way to control and enable these features is using security configurations, see [AUTOTITLE](/code-security/securing-your-organization/introduction-to-securing-your-organization-at-scale/choosing-a-security-configuration-for-your-repositories). +The most effective way to control and enable these features is using security configurations, see [AUTOTITLE](/code-security/concepts/security-at-scale/organization-security). ## Volume/subscription users @@ -51,6 +51,6 @@ If you use volume/subscription billing, then you will need to purchase licenses ## Further reading -* [AUTOTITLE](/code-security/trialing-github-advanced-security/planning-a-trial-of-ghas) -* [AUTOTITLE](/code-security/securing-your-organization/introduction-to-securing-your-organization-at-scale/about-enabling-security-features-at-scale){% ifversion ghec %} -* [AUTOTITLE](/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale){% endif %} +* [AUTOTITLE](/code-security/tutorials/trialing-github-advanced-security/planning-a-trial-of-ghas) +* [AUTOTITLE](/code-security/concepts/security-at-scale/organization-security){% ifversion ghec %} +* [AUTOTITLE](/code-security/tutorials/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale){% endif %} diff --git a/content/billing/how-tos/products/download-license-use.md b/content/billing/how-tos/products/download-license-use.md index 4858c26d2f84..552ac3a4ed5f 100644 --- a/content/billing/how-tos/products/download-license-use.md +++ b/content/billing/how-tos/products/download-license-use.md @@ -17,7 +17,7 @@ category: You can download CSV files with details of paid license use through the {% data variables.product.github %} user interface or the REST API. -For more detailed reports on usage of all paid products, see [AUTOTITLE](/billing/how-tos/products/view-product-use). +For more detailed reports on usage of all paid products, see [AUTOTITLE](/billing/how-tos/products/view-productlicense-use). ## On {% data variables.product.prodname_ghe_cloud %} @@ -48,6 +48,6 @@ For details of the fields included in the report, see [AUTOTITLE](/billing/refer You can retrieve information on paid use of {% data variables.product.prodname_AS %} with the billing API. -* Organization-level data (cloud only), use the `/organizations/{org}/settings/billing/usage` endpoint.{% ifversion fpt or ghec %} For more information, see [AUTOTITLE](/rest/billing/enhanced-billing?apiVersion=2022-11-28).{% endif %} +* Organization-level data (cloud only), use the `/organizations/{org}/settings/billing/usage` endpoint.{% ifversion fpt or ghec %} For more information, see [AUTOTITLE](/rest/billing/usage?apiVersion=2022-11-28#get-billing-usage-report-for-an-organization).{% endif %} -* Enterprise-level data, use the `/enterprises/{enterprise}/settings/billing/usage` endpoint. For more information, see [AUTOTITLE](/enterprise-cloud@latest/rest/enterprise-admin/billing?apiVersion=2022-11-28#get-billing-usage-report-for-an-enterprise) in the {% data variables.product.prodname_ghe_cloud %} documentation. +* Enterprise-level data, use the `/enterprises/{enterprise}/settings/billing/usage` endpoint. For more information, see [AUTOTITLE](/enterprise-cloud@latest/rest/billing/usage?apiVersion=2022-11-28#get-billing-usage-report-for-an-enterprise) in the {% data variables.product.prodname_ghe_cloud %} documentation. diff --git a/content/billing/how-tos/products/estimate-spending.md b/content/billing/how-tos/products/estimate-spending.md index 378371b21834..eb308fb88cf3 100644 --- a/content/billing/how-tos/products/estimate-spending.md +++ b/content/billing/how-tos/products/estimate-spending.md @@ -88,4 +88,4 @@ You can see the total amount of promotions and discounts applied to your account ## Creating a budget -As an enterprise owner or billing manager, you can set the budget for your enterprise, an organization within your enterprise, or a cost center. As an organization owner, you are able to set the budgets for the repositories you manage. See [AUTOTITLE](/billing/managing-your-billing/using-budgets-control-spending#creating-a-budget). +As an enterprise owner or billing manager, you can set the budget for your enterprise, an organization within your enterprise, or a cost center. As an organization owner, you are able to set the budgets for the repositories you manage. See [AUTOTITLE](/billing/how-tos/set-up-budgets#creating-a-budget). diff --git a/content/billing/how-tos/products/manage-ghas-licenses.md b/content/billing/how-tos/products/manage-ghas-licenses.md index 2dbe381a2605..d2fc928f38de 100644 --- a/content/billing/how-tos/products/manage-ghas-licenses.md +++ b/content/billing/how-tos/products/manage-ghas-licenses.md @@ -15,9 +15,9 @@ category: - Manage your plan and licenses --- -There are two different ways to pay for {% data variables.product.prodname_GHAS_cs_and_sp %} licenses: volume/subscription licenses purchased in advance or usage-based metered billing paid in arrears. This article is about volume/subscription licenses. For information about the two different billing models, see [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security). +There are two different ways to pay for {% data variables.product.prodname_GHAS_cs_and_sp %} licenses: volume/subscription licenses purchased in advance or usage-based metered billing paid in arrears. This article is about volume/subscription licenses. For information about the two different billing models, see [AUTOTITLE](/billing/concepts/product-billing/github-advanced-security). -For information about using policies to control use of licenses in your enterprise, see [AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise). +For information about using policies to control use of licenses in your enterprise, see [AUTOTITLE](/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise). ## Changing the size of your license diff --git a/content/billing/how-tos/products/use-cost-centers.md b/content/billing/how-tos/products/use-cost-centers.md index 077f6eabf648..f71bf6df0a3c 100644 --- a/content/billing/how-tos/products/use-cost-centers.md +++ b/content/billing/how-tos/products/use-cost-centers.md @@ -43,11 +43,11 @@ When you create a cost center, you can add **organizations**, **repositories**, ## Adding a budget to a cost center -After you create a cost center, you can add a monthly budget and receive alerts from the cost center to monitor your spending and usage. See [AUTOTITLE](/billing/managing-your-billing/using-budgets-control-spending). +After you create a cost center, you can add a monthly budget and receive alerts from the cost center to monitor your spending and usage. See [AUTOTITLE](/billing/how-tos/set-up-budgets). ## Viewing cost center usage -You can view the usage of your cost centers and download the usage data for further analysis. See [AUTOTITLE](/billing/using-the-enhanced-billing-platform-for-enterprises/gathering-insights-on-your-spending). +You can view the usage of your cost centers and download the usage data for further analysis. See [AUTOTITLE](/billing/tutorials/gather-insights). ## Viewing, editing, and deleting cost centers @@ -62,4 +62,4 @@ You can view, edit, and delete cost centers to manage your business units effect ## Further reading * [AUTOTITLE](/billing/tutorials/control-costs-at-scale) -* [AUTOTITLE](/rest/enterprise-admin/billing) +* [AUTOTITLE](/rest/billing/billing) diff --git a/content/billing/how-tos/products/view-ghas-committers.md b/content/billing/how-tos/products/view-ghas-committers.md index 728920ead683..3befdf6a5674 100644 --- a/content/billing/how-tos/products/view-ghas-committers.md +++ b/content/billing/how-tos/products/view-ghas-committers.md @@ -22,7 +22,7 @@ If you currently use {% data variables.product.prodname_cs_or_sp %}, this tool h If you're considering using {% data variables.product.prodname_cs_or_sp %}, you can use this tool to estimate potential costs to enable {% data variables.product.prodname_cs_or_sp %}. -For more information about billing for {% data variables.product.prodname_AS %}, see [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security). +For more information about billing for {% data variables.product.prodname_AS %}, see [AUTOTITLE](/billing/concepts/product-billing/github-advanced-security). ## Viewing committer information diff --git a/content/billing/how-tos/products/view-productlicense-use.md b/content/billing/how-tos/products/view-productlicense-use.md index f4ff3a472fca..465aa75f2237 100644 --- a/content/billing/how-tos/products/view-productlicense-use.md +++ b/content/billing/how-tos/products/view-productlicense-use.md @@ -42,7 +42,7 @@ category: --- > [!TIP] -> **{% data variables.product.prodname_ghe_server %}** administrators should instead see [AUTOTITLE](/billing/how-tos/products/download-ghas-license-use). +> **{% data variables.product.prodname_ghe_server %}** administrators should instead see [AUTOTITLE](/billing/how-tos/products/download-license-use). ## Viewing a summary of usage @@ -54,7 +54,7 @@ The options available to you vary according to your role and {% data variables.p * If you are an **owner** or **billing manager** of an enterprise, or an organization on {% data variables.product.prodname_team %}, you will also have access to usage data for that organization or enterprise account. {% data variables.product.prodname_ghe_server %}: -* Enterprise owners can access and download usage data for licenses, see [AUTOTITLE](/billing/how-tos/products/download-ghas-license-use). +* Enterprise owners can access and download usage data for licenses, see [AUTOTITLE](/billing/how-tos/products/download-license-use). ### Personal accounts @@ -84,7 +84,7 @@ The metered usage chart and usage break down table both show your current choice {% ifversion fpt or ghec %} > [!TIP] -> For {% data variables.product.prodname_actions %}, you can also view the billable job execution minutes for an individual workflow run. For more information, see [AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time). +> For {% data variables.product.prodname_actions %}, you can also view the billable job execution minutes for an individual workflow run. For more information, see [AUTOTITLE](/actions/how-tos/monitor-workflows/view-job-execution-time). {% endif %} {% ifversion copilot %} @@ -124,6 +124,6 @@ When the chart on the "Metered usage" {% ifversion copilot %}or "AI usage"{% end ## Next steps -* [AUTOTITLE](/billing/reference/usage-reports){% ifversion fpt or ghec %} -* [AUTOTITLE](/billing/managing-your-billing/using-budgets-control-spending) -* [AUTOTITLE](/billing/managing-your-billing/automating-usage-reporting){% endif %} +* [AUTOTITLE](/billing/reference/billing-reports){% ifversion fpt or ghec %} +* [AUTOTITLE](/billing/how-tos/set-up-budgets) +* [AUTOTITLE](/billing/tutorials/automate-usage-reporting){% endif %} diff --git a/content/billing/how-tos/set-up-payment/india-one-time-payments.md b/content/billing/how-tos/set-up-payment/india-one-time-payments.md index 408844a6cc9f..ccaa5e70b04f 100644 --- a/content/billing/how-tos/set-up-payment/india-one-time-payments.md +++ b/content/billing/how-tos/set-up-payment/india-one-time-payments.md @@ -36,7 +36,7 @@ As we work with our payment gateway provider to meet the new requirements, we ar Customers on monthly billing plans will be able to make a one-time payment on the same day their billing cycle usually renews. For example, if you're usually billed on the 7th of each month, you will now be able to make a one-time payment from your account from the 7th of each month. Your first one-time payment will also include any accrued usage from October 2021 onwards. -If you are currently billed monthly, and would like to switch to yearly billing, you can reduce the frequency of your one-time payments. For more information, see [AUTOTITLE](/billing/managing-your-billing/about-the-billing-cycle). +If you are currently billed monthly, and would like to switch to yearly billing, you can reduce the frequency of your one-time payments. For more information, see [AUTOTITLE](/billing/concepts/billing-cycles). ### For customers on yearly billing diff --git a/content/billing/how-tos/set-up-payment/manage-enterprise-invoice.md b/content/billing/how-tos/set-up-payment/manage-enterprise-invoice.md index ec46f9e56cbe..88ff07d89799 100644 --- a/content/billing/how-tos/set-up-payment/manage-enterprise-invoice.md +++ b/content/billing/how-tos/set-up-payment/manage-enterprise-invoice.md @@ -15,7 +15,7 @@ category: - Set up payment --- -{% data variables.product.github %} bills invoiced {% data variables.product.prodname_enterprise %} customers through an enterprise account on {% data variables.product.prodname_dotcom_the_website %}. Each invoice includes a single bill charge for all of your paid {% data variables.product.prodname_dotcom_the_website %} services and any {% data variables.product.prodname_ghe_server %} instances. For more information, see [AUTOTITLE](/billing/managing-your-billing/about-billing-for-your-enterprise). +{% data variables.product.github %} bills invoiced {% data variables.product.prodname_enterprise %} customers through an enterprise account on {% data variables.product.prodname_dotcom_the_website %}. Each invoice includes a single bill charge for all of your paid {% data variables.product.prodname_dotcom_the_website %} services and any {% data variables.product.prodname_ghe_server %} instances. For more information, see [AUTOTITLE](/billing/concepts/enterprise-billing/billing-for-enterprises). ## Viewing your current invoice diff --git a/content/billing/how-tos/set-up-payment/set-up-vs-subscription.md b/content/billing/how-tos/set-up-payment/set-up-vs-subscription.md index b0ca82b649de..e412e11af408 100644 --- a/content/billing/how-tos/set-up-payment/set-up-vs-subscription.md +++ b/content/billing/how-tos/set-up-payment/set-up-vs-subscription.md @@ -17,7 +17,7 @@ category: > [!NOTE] Customers with a {% data variables.product.prodname_vs %} bundle can **switch to usage-based billing** for {% data variables.product.prodname_enterprise %} licenses. This allows you to pay for licenses on a flexible monthly cycle for users who are not part of your {% data variables.product.prodname_vs %} subscription. See [AUTOTITLE](/billing/concepts/enterprise-billing/usage-based-licenses). -{% data reusables.enterprise-accounts.vss-ghe-description %} See [AUTOTITLE](/billing/managing-billing-for-your-products/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise). +{% data reusables.enterprise-accounts.vss-ghe-description %} See [AUTOTITLE](/billing/concepts/enterprise-billing/visual-studio-subs). ## Prerequisites @@ -25,7 +25,7 @@ category: * [{% data variables.product.prodname_vs %} Subscriptions and Benefits](https://visualstudio.microsoft.com/subscriptions/) on the {% data variables.product.prodname_vs %} website * [Overview of admin responsibilities](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) in Microsoft Docs. -* Your team must have an enterprise on {% data variables.product.github %}, see [AUTOTITLE](/admin/overview/about-enterprise-accounts). +* Your team must have an enterprise on {% data variables.product.github %}, see [AUTOTITLE](/admin/concepts/enterprise-fundamentals/enterprise-accounts). * If you're not sure whether your team has an enterprise, contact your {% data variables.product.github %} administrator. * If you're not sure who on your team is responsible for {% data variables.product.github %} services, contact {% data variables.contact.contact_enterprise_sales %}. @@ -35,7 +35,7 @@ To set up {% data variables.visual_studio.prodname_vss_ghe %}, members of your t One person may be able to complete the tasks because the person has all of the roles, but you may need to coordinate the tasks with multiple people. For more information, see [AUTOTITLE](/billing/reference/roles-for-visual-studio). -1. A {% data variables.product.github %} enterprise owner must create at least one organization in your enterprise. For more information, see [AUTOTITLE](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise){% ifversion ghes %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %} +1. A {% data variables.product.github %} enterprise owner must create at least one organization in your enterprise. For more information, see [AUTOTITLE](/enterprise-cloud@latest/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise){% ifversion ghes %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %} 1. The {% data variables.product.prodname_vs %} subscription admin must assign a license for {% data variables.product.prodname_vs %} to a subscriber in {% data variables.visual_studio.prodname_vss_admin_portal_with_url %}. For more information, see [Overview of the {% data variables.product.prodname_vs %} Subscriptions Administrator Portal](https://docs.microsoft.com/en-us/visualstudio/subscriptions/using-admin-portal) and [Assign {% data variables.product.prodname_vs %} Licenses in the {% data variables.product.prodname_vs %} Subscriptions Administration Portal](https://docs.microsoft.com/en-us/visualstudio/subscriptions/assign-license) in Microsoft Docs. @@ -47,12 +47,12 @@ One person may be able to complete the tasks because the person has all of the r > [!TIP] > * While not required, we recommend that the organization owner sends an invitation to the same email address used for the subscriber's User Primary Name (UPN). When the email address on {% data variables.product.github %} matches the subscriber's UPN, you can ensure that another enterprise does not claim the subscriber's license. - > * If the subscriber accepts the invitation to the organization with an existing personal account on {% data variables.product.github %}, we recommend that the subscriber add the email address they use for {% data variables.product.prodname_vs %} to their personal account on {% data variables.product.github %}. For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account). + > * If the subscriber accepts the invitation to the organization with an existing personal account on {% data variables.product.github %}, we recommend that the subscriber add the email address they use for {% data variables.product.prodname_vs %} to their personal account on {% data variables.product.github %}. For more information, see [AUTOTITLE](/account-and-profile/how-tos/email-preferences/adding-an-email-address-to-your-github-account). > * If the organization owner must invite a large number of subscribers, a script may make the process faster. For more information, see [the sample PowerShell script](https://github.com/github/platform-samples/blob/master/api/powershell/invite_members_to_org.ps1) in the `github/platform-samples` repository. 1. If any enterprise members aren't automatically matched to their {% data variables.product.prodname_vs %} account, an enterprise owner can match the accounts manually on {% data variables.product.github %}. See [Reconciling users across {% data variables.product.prodname_vs %} and {% data variables.product.github %}](#reconciling-users-across-visual-studio-and-github). -After {% data variables.visual_studio.prodname_vss_ghe %} is set up for subscribers on your team, enterprise owners can review licensing information on {% data variables.product.github %}. For more information, see [AUTOTITLE](/billing/managing-the-plan-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account). +After {% data variables.visual_studio.prodname_vss_ghe %} is set up for subscribers on your team, enterprise owners can review licensing information on {% data variables.product.github %}. For more information, see [AUTOTITLE](/billing/how-tos/manage-plan-and-licenses/view-enterprise-usage). ## Reconciling users across {% data variables.product.prodname_vs %} and {% data variables.product.github %} @@ -79,9 +79,9 @@ When you've identified {% data variables.product.github %} users who aren't corr ## Viewing available licenses -You can view the number of {% data variables.product.prodname_enterprise %} licenses available to your enterprise on {% data variables.location.product_location %}. The list of pending invitations includes subscribers who are not yet members of at least one organization in your enterprise. For more information, see [AUTOTITLE](/billing/managing-the-plan-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account) and [AUTOTITLE](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#viewing-members-and-outside-collaborators). +You can view the number of {% data variables.product.prodname_enterprise %} licenses available to your enterprise on {% data variables.location.product_location %}. The list of pending invitations includes subscribers who are not yet members of at least one organization in your enterprise. For more information, see [AUTOTITLE](/billing/how-tos/manage-plan-and-licenses/view-enterprise-usage) and [AUTOTITLE](/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#viewing-members-and-outside-collaborators). -> [!TIP] If you download a CSV file with your enterprise's license usage in step 6 of [AUTOTITLE](/billing/managing-the-plan-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account#viewing-the-subscription-and-usage-for-your-enterprise-account), any members with a missing value for the "Name" or "Profile" columns have not yet accepted an invitation to join an organization within the enterprise. +> [!TIP] If you download a CSV file with your enterprise's license usage in step 6 of [AUTOTITLE](/billing/how-tos/manage-plan-and-licenses/view-enterprise-usage#viewing-the-subscription-and-usage-for-your-enterprise-account), any members with a missing value for the "Name" or "Profile" columns have not yet accepted an invitation to join an organization within the enterprise. You can also see pending {% data variables.product.prodname_enterprise %} invitations to subscribers in {% data variables.visual_studio.prodname_vss_admin_portal_with_url %}. diff --git a/content/billing/how-tos/troubleshooting/declined-card.md b/content/billing/how-tos/troubleshooting/declined-card.md index 463fcd213176..8d372ab46e1b 100644 --- a/content/billing/how-tos/troubleshooting/declined-card.md +++ b/content/billing/how-tos/troubleshooting/declined-card.md @@ -38,13 +38,13 @@ For more detailed instructions, see [Managing payment information](/billing/how- Some international banks place restrictions on international, e-commerce, and automatically recurring transactions. If you're having trouble making a payment with your international credit card, call your bank to see if there are any restrictions on your card. -We also support payments through PayPal. For more information, see [AUTOTITLE](/billing/managing-your-billing/managing-your-payment-and-billing-information). +We also support payments through PayPal. For more information, see [AUTOTITLE](/billing/how-tos/set-up-payment/manage-payment-info). ## 3. Contact your bank for details about the transaction If your card is still valid, you have no restrictions on it, or the restrictions don't apply to your payments for {% data variables.product.company_short %} services, you need to call your bank. Your bank can provide additional information about declined payments if you specifically ask about the attempted transaction. Important information to provide includes: -* **The amount you're being charged.** The amount for your subscription appears on your account's receipts. For more information, see [AUTOTITLE](/billing/managing-your-billing/managing-your-payment-and-billing-information). +* **The amount you're being charged.** The amount for your subscription appears on your account's receipts. For more information, see [AUTOTITLE](/billing/how-tos/set-up-payment/manage-payment-info). * **The date when {% data variables.product.company_short %} bills you.** Your account's billing date appears on your receipts. * **The transaction ID number.** Your account's transaction ID appears on your receipts. * **The merchant name.** The merchant name is {% data variables.product.prodname_dotcom %}. diff --git a/content/billing/how-tos/troubleshooting/enterprise-license-usage.md b/content/billing/how-tos/troubleshooting/enterprise-license-usage.md index 9db903a651b4..f612de238779 100644 --- a/content/billing/how-tos/troubleshooting/enterprise-license-usage.md +++ b/content/billing/how-tos/troubleshooting/enterprise-license-usage.md @@ -16,7 +16,7 @@ category: ## About unexpected license usage -If the number of consumed licenses for your enterprise is unexpected, you can review your consumed license report to audit your license usage across all your enterprise deployments and subscriptions. For more information, see [AUTOTITLE](/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise) and [AUTOTITLE](/billing/reference/license-usage-calculation). +If the number of consumed licenses for your enterprise is unexpected, you can review your consumed license report to audit your license usage across all your enterprise deployments and subscriptions. For more information, see [AUTOTITLE](/billing/how-tos/manage-plan-and-licenses/view-enterprise-usage) and [AUTOTITLE](/billing/reference/enterprise-license-troubleshooting). > [!NOTE] For privacy reasons, enterprise owners cannot directly access the details of user accounts unless you use {% data variables.product.prodname_emus %}. @@ -28,12 +28,12 @@ To ensure that each user is only consuming a single {% ifversion enterprise-lice 1. To help identify users that are consuming multiple {% ifversion enterprise-licensing-language %}licenses{% else %}seats{% endif %}, if your enterprise uses verified domains for {% data variables.product.prodname_ghe_cloud %}, review the list of enterprise members who do not have an email address from a verified domain associated with their account on {% data variables.product.prodname_ghe_cloud %}. - Often, these are the users who erroneously consume more than one {% ifversion enterprise-licensing-language %}license{% else %}licensed seat{% endif %}. For more information, see [AUTOTITLE](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#viewing-members-without-an-email-address-from-a-verified-domain). + Often, these are the users who erroneously consume more than one {% ifversion enterprise-licensing-language %}license{% else %}licensed seat{% endif %}. For more information, see [AUTOTITLE](/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#viewing-members-without-an-email-address-from-a-verified-domain). > [!NOTE] - > To make troubleshooting easier, we recommend using verified domains with your enterprise account on {% data variables.product.prodname_ghe_cloud %}. For more information, see [AUTOTITLE](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise). + > To make troubleshooting easier, we recommend using verified domains with your enterprise account on {% data variables.product.prodname_ghe_cloud %}. For more information, see [AUTOTITLE](/enterprise-cloud@latest/admin/configuring-settings/configuring-user-applications-for-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise). -1. After you identify users who are consuming multiple {% ifversion enterprise-licensing-language %}licenses{% else %}seats{% endif %}, make sure that the same email address is associated with all of the user's accounts. For more information about which email addresses must match, see [AUTOTITLE](/billing/reference/license-usage-calculation). -1. If an email address was recently updated or verified to correct a mismatch, view the timestamp of the last license sync job. If a job hasn't run since the correction was made, manually trigger a new job. For more information, see [AUTOTITLE](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud). +1. After you identify users who are consuming multiple {% ifversion enterprise-licensing-language %}licenses{% else %}seats{% endif %}, make sure that the same email address is associated with all of the user's accounts. For more information about which email addresses must match, see [AUTOTITLE](/billing/reference/enterprise-license-troubleshooting). +1. If an email address was recently updated or verified to correct a mismatch, view the timestamp of the last license sync job. If a job hasn't run since the correction was made, manually trigger a new job. For more information, see [AUTOTITLE](/billing/how-tos/manage-server-licenses/sync-license-usage). If you still have questions about your consumed licenses after reviewing the troubleshooting information above, you can contact {% data variables.contact.github_support %} through the {% data variables.contact.contact_enterprise_portal %}. diff --git a/content/billing/how-tos/troubleshooting/locked-account.md b/content/billing/how-tos/troubleshooting/locked-account.md index a3c0b5e694a4..9477bacbb8ba 100644 --- a/content/billing/how-tos/troubleshooting/locked-account.md +++ b/content/billing/how-tos/troubleshooting/locked-account.md @@ -26,7 +26,7 @@ category: You can unlock and access your account by updating your account's payment method and resuming paid status. We do not ask you to pay for the time elapsed in locked mode. -You can downgrade your user account or organization to {% data variables.product.prodname_free_team %} to continue with the same advanced features in public repositories. For more information, see [AUTOTITLE](/billing/managing-the-plan-for-your-github-account/downgrading-your-accounts-plan). +You can downgrade your user account or organization to {% data variables.product.prodname_free_team %} to continue with the same advanced features in public repositories. For more information, see [AUTOTITLE](/billing/how-tos/manage-plan-and-licenses/downgrade-plan). ## Unlocking an account's features due to a declined payment From 6cd83aa66cf445c518e7f2b9a51166fb91442bb7 Mon Sep 17 00:00:00 2001 From: Kevin Heis Date: Thu, 9 Jul 2026 06:41:52 -0700 Subject: [PATCH 09/17] Update redirected internal links in github-models (#62120) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- content/github-models/about-github-models.md | 4 ++-- .../github-models-at-scale/use-models-at-scale.md | 2 +- .../using-your-own-api-keys-in-github-models.md | 2 +- content/github-models/quickstart.md | 4 ++-- .../use-github-models/evaluating-ai-models.md | 2 +- .../use-github-models/prototyping-with-ai-models.md | 8 ++++---- 6 files changed, 11 insertions(+), 11 deletions(-) diff --git a/content/github-models/about-github-models.md b/content/github-models/about-github-models.md index 8667020d63c0..b84ecffb9009 100644 --- a/content/github-models/about-github-models.md +++ b/content/github-models/about-github-models.md @@ -58,7 +58,7 @@ Use the Playground to quickly explore models and test prompt ideas in real time. ## Billing -For more information about billing for {% data variables.product.prodname_github_models %}, see [AUTOTITLE](/billing/managing-billing-for-your-products/about-billing-for-github-models). +For more information about billing for {% data variables.product.prodname_github_models %}, see [AUTOTITLE](/billing/concepts/product-billing/github-models). ## Join the community @@ -71,4 +71,4 @@ To learn how others are using {% data variables.product.prodname_github_models % * [AUTOTITLE](/github-models/use-github-models/prototyping-with-ai-models) * [AUTOTITLE](/github-models/use-github-models/optimizing-your-ai-powered-app-with-github-models) * [AUTOTITLE](/github-models/use-github-models/evaluating-ai-models) -* [AUTOTITLE](/billing/managing-billing-for-your-products/about-billing-for-github-models) +* [AUTOTITLE](/billing/concepts/product-billing/github-models) diff --git a/content/github-models/github-models-at-scale/use-models-at-scale.md b/content/github-models/github-models-at-scale/use-models-at-scale.md index 23179c833377..ffb2b41c0766 100644 --- a/content/github-models/github-models-at-scale/use-models-at-scale.md +++ b/content/github-models/github-models-at-scale/use-models-at-scale.md @@ -122,7 +122,7 @@ Large software development projects often contain issues full of technical detai 1. **Call your prompt in a workflow** - For information on creating workflows, see [AUTOTITLE](/actions/writing-workflows). + For information on creating workflows, see [AUTOTITLE](/actions/how-tos/write-workflows). You need to set `models: read` permission to allow a prompt to be called in a workflow. diff --git a/content/github-models/github-models-at-scale/using-your-own-api-keys-in-github-models.md b/content/github-models/github-models-at-scale/using-your-own-api-keys-in-github-models.md index f629837dba40..feea04b32bea 100644 --- a/content/github-models/github-models-at-scale/using-your-own-api-keys-in-github-models.md +++ b/content/github-models/github-models-at-scale/using-your-own-api-keys-in-github-models.md @@ -18,7 +18,7 @@ category: You can bring your own API keys (BYOK) to {% data variables.product.prodname_github_models %}, and enable teams to use your preferred large language model (LLM) providers across tools like Prompts, Playground, and Models in Actions. For more information about {% data variables.product.prodname_github_models %}, see [AUTOTITLE](/github-models/about-github-models). -To learn about billing and pricing, see [AUTOTITLE](/billing/managing-billing-for-your-products/about-billing-for-github-models). +To learn about billing and pricing, see [AUTOTITLE](/billing/concepts/product-billing/github-models). ## Why bring your own API keys? diff --git a/content/github-models/quickstart.md b/content/github-models/quickstart.md index a03d90f734b0..a1c980d88cb8 100644 --- a/content/github-models/quickstart.md +++ b/content/github-models/quickstart.md @@ -109,7 +109,7 @@ To call models programmatically, you’ll need: 1. Commit and push to trigger the workflow. -This example shows how to send a prompt to a model and use the response in your continuous integration (CI) workflows. For more advanced use cases, such as summarizing issues, detecting missing reproduction steps for bug reports, or responding to pull requests, see [AUTOTITLE](/github-models/use-github-models/integrating-ai-models-into-your-development-workflow). +This example shows how to send a prompt to a model and use the response in your continuous integration (CI) workflows. For more advanced use cases, such as summarizing issues, detecting missing reproduction steps for bug reports, or responding to pull requests, see [AUTOTITLE](/copilot/how-tos/copilot-on-github/set-up-copilot/configure-access-to-ai-models). ## Step 4: Save your first prompt file @@ -196,4 +196,4 @@ Evaluations help you measure how different models respond to the same inputs so * [Browse the model catalog](https://github.com/marketplace?type=models) * [AUTOTITLE](/github-models/use-github-models/storing-prompts-in-github-repositories) * [AUTOTITLE](/github-models/use-github-models/evaluating-ai-models) -* [AUTOTITLE](/github-models/use-github-models/integrating-ai-models-into-your-development-workflow#using-ai-models-with-github-actions) +* [AUTOTITLE](/copilot/how-tos/copilot-on-github/set-up-copilot/configure-access-to-ai-models) diff --git a/content/github-models/use-github-models/evaluating-ai-models.md b/content/github-models/use-github-models/evaluating-ai-models.md index c1aefb27a3fd..e25602bb03e3 100644 --- a/content/github-models/use-github-models/evaluating-ai-models.md +++ b/content/github-models/use-github-models/evaluating-ai-models.md @@ -271,4 +271,4 @@ Committing your prompt configuration makes it easy to reuse, collaborate, and it ## Further reading * [AUTOTITLE](/github-models/use-github-models/storing-prompts-in-github-repositories) -* [AUTOTITLE](/github-models/use-github-models/integrating-ai-models-into-your-development-workflow) +* [AUTOTITLE](/copilot/how-tos/copilot-on-github/set-up-copilot/configure-access-to-ai-models) diff --git a/content/github-models/use-github-models/prototyping-with-ai-models.md b/content/github-models/use-github-models/prototyping-with-ai-models.md index 98155d3b35bd..a032b555ca61 100644 --- a/content/github-models/use-github-models/prototyping-with-ai-models.md +++ b/content/github-models/use-github-models/prototyping-with-ai-models.md @@ -10,9 +10,9 @@ category: - Build with AI models --- -If you want to develop a generative AI application, you can use {% data variables.product.prodname_github_models %} to find and experiment with AI models for free. Once you are ready to bring your application to production, [opt in to paid usage](/billing/managing-billing-for-your-products/about-billing-for-github-models) for your enterprise. +If you want to develop a generative AI application, you can use {% data variables.product.prodname_github_models %} to find and experiment with AI models for free. Once you are ready to bring your application to production, [opt in to paid usage](/billing/concepts/product-billing/github-models) for your enterprise. -Organization owners can integrate their preferred custom models into {% data variables.product.prodname_github_models %}, by using an organization's own LLM API keys. See [AUTOTITLE](/github-models/github-models-at-scale/set-up-custom-model-integration-models-byok). +Organization owners can integrate their preferred custom models into {% data variables.product.prodname_github_models %}, by using an organization's own LLM API keys. See [AUTOTITLE](/github-models/github-models-at-scale/using-your-own-api-keys-in-github-models). See also [AUTOTITLE](/github-models/responsible-use-of-github-models). @@ -134,8 +134,8 @@ If you prefer to experiment with AI models in your IDE, you can install the AI T ## Going to production The free rate limits provided in the playground and API usage are intended to help you get started with experimentation. When you are ready to move beyond the free offering, you have two options for accessing AI models beyond the free limits: -* You can opt in to paid usage for {% data variables.product.prodname_github_models %}, allowing your organization to access increased rate limits, larger context windows, and additional features. See [AUTOTITLE](/billing/managing-billing-for-your-products/about-billing-for-github-models). -* If you have an existing OpenAI or Azure subscription, you can bring your own API keys (BYOK) to access custom models. Billing and usage are managed directly through your provider account, such as your Azure Subscription ID. See [AUTOTITLE](/github-models/github-models-at-scale/set-up-custom-model-integration-models-byok). +* You can opt in to paid usage for {% data variables.product.prodname_github_models %}, allowing your organization to access increased rate limits, larger context windows, and additional features. See [AUTOTITLE](/billing/concepts/product-billing/github-models). +* If you have an existing OpenAI or Azure subscription, you can bring your own API keys (BYOK) to access custom models. Billing and usage are managed directly through your provider account, such as your Azure Subscription ID. See [AUTOTITLE](/github-models/github-models-at-scale/using-your-own-api-keys-in-github-models). ## Rate limits From a5290f876bdfa8ec062ab38043de2b886e17be9e Mon Sep 17 00:00:00 2001 From: Kevin Heis Date: Thu, 9 Jul 2026 06:41:59 -0700 Subject: [PATCH 10/17] Update redirected internal links in pages (#62118) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .../about-custom-domains-and-github-pages.md | 2 +- .../troubleshooting-custom-domains-and-github-pages.md | 2 +- .../verifying-your-custom-domain-for-github-pages.md | 2 +- ...ring-a-publishing-source-for-your-github-pages-site.md | 6 +++--- .../github-pages-limits.md | 2 +- .../using-custom-workflows-with-github-pages.md | 4 ++-- .../what-is-github-pages.md | 4 ++-- .../about-jekyll-build-errors-for-github-pages-sites.md | 8 ++++---- .../creating-a-github-pages-site-with-jekyll.md | 2 +- 9 files changed, 16 insertions(+), 16 deletions(-) diff --git a/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md b/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md index 9dff54e165ff..9670903a630a 100644 --- a/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md +++ b/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md @@ -75,7 +75,7 @@ An apex domain is configured with an `A`, `ALIAS`, or `ANAME` record through you There are a couple of reasons your site might be automatically disabled. -* If you downgrade from {% data variables.product.prodname_pro %} to {% data variables.product.prodname_free_user %}, any {% data variables.product.prodname_pages %} sites that are currently published from private repositories in your account will be unpublished. For more information, see [AUTOTITLE](/billing/managing-the-plan-for-your-github-account/downgrading-your-accounts-plan). +* If you downgrade from {% data variables.product.prodname_pro %} to {% data variables.product.prodname_free_user %}, any {% data variables.product.prodname_pages %} sites that are currently published from private repositories in your account will be unpublished. For more information, see [AUTOTITLE](/billing/how-tos/manage-plan-and-licenses/downgrade-plan). * If you transfer a private repository to a personal account that is using {% data variables.product.prodname_free_user %}, the repository will lose access to the {% data variables.product.prodname_pages %} feature, and the currently published {% data variables.product.prodname_pages %} site will be unpublished. For more information, see [AUTOTITLE](/repositories/creating-and-managing-repositories/transferring-a-repository). ## Further reading diff --git a/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md b/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md index 8f57306edec7..6a547caba7ef 100644 --- a/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md +++ b/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md @@ -65,7 +65,7 @@ If you're using Certification Authority Authorization (CAA) records, at least on ## URL formatting on Linux -If the URL for your site contains a username or organization name that begins or ends with a dash, or contains consecutive dashes, people browsing with Linux will receive a server error when they attempt to visit your site. To fix this, change your {% data variables.product.github %} username to remove non-alphanumeric characters. For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username). +If the URL for your site contains a username or organization name that begins or ends with a dash, or contains consecutive dashes, people browsing with Linux will receive a server error when they attempt to visit your site. To fix this, change your {% data variables.product.github %} username to remove non-alphanumeric characters. For more information, see [AUTOTITLE](/account-and-profile/concepts/username-changes). ## Browser cache diff --git a/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md b/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md index b225c10f309a..a6b116d44f6f 100644 --- a/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md +++ b/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md @@ -20,7 +20,7 @@ When you verify a domain, any immediate subdomains are also included in the veri {% data reusables.pages.wildcard-dns-warning %} -It's also possible to verify a domain for your organization{% ifversion ghec %} or enterprise{% endif %}, which displays a "Verified" badge on the organization {% ifversion ghec %}or enterprise{% endif %} profile{% ifversion ghec %} and, on {% data variables.product.prodname_ghe_cloud %}, allows you to restrict notifications to email addresses using the verified domain{% endif %}. For more information, see [AUTOTITLE](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization){% ifversion ghec %} and [AUTOTITLE](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise){% endif %}. +It's also possible to verify a domain for your organization{% ifversion ghec %} or enterprise{% endif %}, which displays a "Verified" badge on the organization {% ifversion ghec %}or enterprise{% endif %} profile{% ifversion ghec %} and, on {% data variables.product.prodname_ghe_cloud %}, allows you to restrict notifications to email addresses using the verified domain{% endif %}. For more information, see [AUTOTITLE](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization){% ifversion ghec %} and [AUTOTITLE](/enterprise-cloud@latest/admin/configuring-settings/configuring-user-applications-for-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise){% endif %}. ### Verifying a domain that is already taken diff --git a/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md b/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md index ad6bc5eefa3a..4e13b44cf66a 100644 --- a/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md +++ b/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md @@ -47,7 +47,7 @@ If you choose the `docs` folder on any branch as your publishing source, then la Your {% data variables.product.prodname_pages %} site will always be deployed with a {% data variables.product.prodname_actions %} workflow run, even if you've configured your {% data variables.product.prodname_pages %} site to be built using a different CI tool. Most external CI workflows "deploy" to {% data variables.product.prodname_pages %} by committing the build output to the `gh-pages` branch of the repository, and typically include a `.nojekyll` file. When this happens, the {% data variables.product.prodname_actions %} workflow will detect the state that the branch does not need a build step, and will execute only the steps necessary to deploy the site to {% data variables.product.prodname_pages %} servers. -To find potential errors with either the build or deployment, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. For more information, see [AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history). For more information about how to re-run the workflow in case of an error, see [AUTOTITLE](/actions/managing-workflow-runs/re-running-workflows-and-jobs). +To find potential errors with either the build or deployment, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. For more information, see [AUTOTITLE](/actions/how-tos/monitor-workflows/view-workflow-run-history). For more information about how to re-run the workflow in case of an error, see [AUTOTITLE](/actions/how-tos/manage-workflow-runs/re-run-workflows-and-jobs). {% endif %} @@ -75,7 +75,7 @@ When you configure your site to publish with {% data variables.product.prodname_ 1. Use the [`actions/upload-pages-artifact`](https://github.com/actions/upload-pages-artifact) action to upload the static files as an artifact. 1. If the workflow was triggered by a push to the default branch, use the [`actions/deploy-pages`](https://github.com/actions/deploy-pages) action to deploy the artifact. This step is skipped if the workflow was triggered by a pull request. -The workflow templates use a deployment environment called `github-pages`. If your repository does not already include an environment called `github-pages`, the environment will be created automatically. We recommend that you add a deployment protection rule so that only the default branch can deploy to this environment. For more information, see [AUTOTITLE](/actions/deployment/targeting-different-environments/using-environments-for-deployment). +The workflow templates use a deployment environment called `github-pages`. If your repository does not already include an environment called `github-pages`, the environment will be created automatically. We recommend that you add a deployment protection rule so that only the default branch can deploy to this environment. For more information, see [AUTOTITLE](/actions/how-tos/deploy/configure-and-manage-deployments/manage-environments). {% ifversion fpt or ghec %} @@ -86,4 +86,4 @@ The workflow templates use a deployment environment called `github-pages`. If yo ### Troubleshooting publishing with a custom {% data variables.product.prodname_actions %} workflow -For information about how to troubleshoot your {% data variables.product.prodname_actions %} workflow, see [AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting). +For information about how to troubleshoot your {% data variables.product.prodname_actions %} workflow, see [AUTOTITLE](/actions/how-tos/monitor-workflows). diff --git a/content/pages/getting-started-with-github-pages/github-pages-limits.md b/content/pages/getting-started-with-github-pages/github-pages-limits.md index d56cd8320c2d..4a3bbb2de3d2 100644 --- a/content/pages/getting-started-with-github-pages/github-pages-limits.md +++ b/content/pages/getting-started-with-github-pages/github-pages-limits.md @@ -41,7 +41,7 @@ If you're a {% data variables.enterprise.prodname_managed_user %}, your use of { * {% data variables.product.prodname_pages %} sites are always privately published, and you cannot change this visibility. For more information, see [AUTOTITLE](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site). * You cannot create an organization site (a site published from a repository named `.github.io`) -For more information about {% data variables.product.prodname_emus %}, see [AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users). +For more information about {% data variables.product.prodname_emus %}, see [AUTOTITLE](/admin/concepts/identity-and-access-management/enterprise-managed-users). {% endif %} diff --git a/content/pages/getting-started-with-github-pages/using-custom-workflows-with-github-pages.md b/content/pages/getting-started-with-github-pages/using-custom-workflows-with-github-pages.md index 1ac66fca450b..78c7bc49fef7 100644 --- a/content/pages/getting-started-with-github-pages/using-custom-workflows-with-github-pages.md +++ b/content/pages/getting-started-with-github-pages/using-custom-workflows-with-github-pages.md @@ -26,7 +26,7 @@ To use the action place this snippet under your `jobs` in the desired workflow. uses: actions/configure-pages@v5 ``` -This action helps support deployment from any static site generator to {% data variables.product.prodname_pages %}. To make this process less repetitive you can use workflow templates for some of the most widely used static site generators. For more information, see [AUTOTITLE](/actions/learn-github-actions/using-starter-workflows). +This action helps support deployment from any static site generator to {% data variables.product.prodname_pages %}. To make this process less repetitive you can use workflow templates for some of the most widely used static site generators. For more information, see [AUTOTITLE](/actions/how-tos/write-workflows/use-workflow-templates). ## Configuring the `upload-pages-artifact` action @@ -163,4 +163,4 @@ jobs: # ... ``` -You can define your jobs to be run on different runners, sequentially, or in parallel. For more information, see [AUTOTITLE](/actions/using-jobs). +You can define your jobs to be run on different runners, sequentially, or in parallel. For more information, see [AUTOTITLE](/actions/how-tos/write-workflows/choose-what-workflows-do). diff --git a/content/pages/getting-started-with-github-pages/what-is-github-pages.md b/content/pages/getting-started-with-github-pages/what-is-github-pages.md index 3976ab661898..5a2641cc3d6e 100644 --- a/content/pages/getting-started-with-github-pages/what-is-github-pages.md +++ b/content/pages/getting-started-with-github-pages/what-is-github-pages.md @@ -74,7 +74,7 @@ If you publish your site privately, the URL for your site will be different. For {% endif %} {% ifversion ghes %} -For more information, see [AUTOTITLE](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation) or contact your site administrator. +For more information, see [AUTOTITLE](/admin/configuring-settings/hardening-security-for-your-enterprise/enabling-subdomain-isolation) or contact your site administrator. {% endif %} {% ifversion fpt or ghec %} @@ -89,7 +89,7 @@ You can host your site on {% data variables.product.prodname_dotcom %}'s `github ## Data collection -When a {% data variables.product.prodname_pages %} site is visited, the visitor's IP address is logged and stored for security purposes, regardless of whether the visitor has signed into {% data variables.product.prodname_dotcom %} or not. For more information about {% data variables.product.prodname_dotcom %}'s security practices, see [{% data variables.product.prodname_dotcom %} Privacy Statement](/site-policy/privacy-policies/github-privacy-statement). +When a {% data variables.product.prodname_pages %} site is visited, the visitor's IP address is logged and stored for security purposes, regardless of whether the visitor has signed into {% data variables.product.prodname_dotcom %} or not. For more information about {% data variables.product.prodname_dotcom %}'s security practices, see [{% data variables.product.prodname_dotcom %} Privacy Statement](/site-policy/privacy-policies/github-general-privacy-statement). {% endif %} ## Further reading diff --git a/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md b/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md index 042bc01194d0..0aa7729677e0 100644 --- a/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md +++ b/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md @@ -21,7 +21,7 @@ category: ## About Jekyll build errors If you are publishing from a branch, sometimes {% data variables.product.prodname_pages %} will not attempt to build your site after you push changes to your site's publishing source.{% ifversion fpt or ghec %} -* The person who pushed the changes hasn't verified their email address. For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/verifying-your-email-address).{% endif %} +* The person who pushed the changes hasn't verified their email address. For more information, see [AUTOTITLE](/account-and-profile/how-tos/email-preferences/verifying-your-email-address).{% endif %} * You're pushing with a deploy key. If you want to automate pushes to your site's repository, you can set up a machine user instead. For more information, see [AUTOTITLE](/authentication/connecting-to-github-with-ssh/managing-deploy-keys#machine-users). * You're using a CI service that isn't configured to build your publishing source. For example, Travis CI won't build the `gh-pages` branch unless you add the branch to a safe list. For more information, see [Customizing the build](https://docs.travis-ci.com/user/customizing-the-build/#safelisting-or-blocklisting-branches) on Travis CI, or your CI service's documentation. @@ -42,7 +42,7 @@ For more information about troubleshooting build errors, see [AUTOTITLE](/pages/ ## Viewing Jekyll build error messages with {% data variables.product.prodname_actions %} -By default, your {% data variables.product.prodname_pages %} site is built and deployed with a {% data variables.product.prodname_actions %} workflow run unless you've configured your {% data variables.product.prodname_pages %} site to use a different CI tool. To find potential build errors, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. For more information, see [AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history). For more information about how to re-run the workflow in case of an error, see [AUTOTITLE](/actions/managing-workflow-runs/re-running-workflows-and-jobs). +By default, your {% data variables.product.prodname_pages %} site is built and deployed with a {% data variables.product.prodname_actions %} workflow run unless you've configured your {% data variables.product.prodname_pages %} site to use a different CI tool. To find potential build errors, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. For more information, see [AUTOTITLE](/actions/how-tos/monitor-workflows/view-workflow-run-history). For more information about how to re-run the workflow in case of an error, see [AUTOTITLE](/actions/how-tos/manage-workflow-runs/re-run-workflows-and-jobs). {% endif %} {% ifversion build-pages-with-actions %}{% else %} @@ -60,13 +60,13 @@ We recommend testing your site locally, which allows you to see build error mess If you are publishing from a branch, when you create a pull request to update your publishing source on {% data variables.product.github %}, you can see build error messages on the **Checks** tab of the pull request. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks). -If you are publishing with a custom {% data variables.product.prodname_actions %} workflow, in order to see build error messages in your pull request, you must configure your workflow to run on the `pull_request` trigger. When you do this, we recommend that you skip any deploy steps if the workflow was triggered by the `pull_request` event. This will allow you to see any build errors without deploying the changes from your pull request to your site. For more information, see [AUTOTITLE](/actions/using-workflows/events-that-trigger-workflows#pull_request) and [AUTOTITLE](/actions/learn-github-actions/expressions). +If you are publishing with a custom {% data variables.product.prodname_actions %} workflow, in order to see build error messages in your pull request, you must configure your workflow to run on the `pull_request` trigger. When you do this, we recommend that you skip any deploy steps if the workflow was triggered by the `pull_request` event. This will allow you to see any build errors without deploying the changes from your pull request to your site. For more information, see [AUTOTITLE](/actions/reference/workflows-and-actions/events-that-trigger-workflows#pull_request) and [AUTOTITLE](/actions/reference/workflows-and-actions/expressions). ## Viewing Jekyll build errors by email If you are publishing from a branch, when you push changes to your publishing source on {% data variables.product.github %}, {% data variables.product.prodname_pages %} will attempt to build your site. If the build fails, you'll receive an email at your primary email address. {% data reusables.pages.build-failure-email-server %} -If you are publishing with a custom {% data variables.product.prodname_actions %} workflow, in order to receive emails about build errors in your pull request, you must configure your workflow to run on the `pull_request` trigger. When you do this, we recommend that you skip any deploy steps if the workflow was triggered by the `pull_request` event. This will allow you to see any build errors without deploying the changes from your pull request to your site. For more information, see [AUTOTITLE](/actions/using-workflows/events-that-trigger-workflows#pull_request) and [AUTOTITLE](/actions/learn-github-actions/expressions). +If you are publishing with a custom {% data variables.product.prodname_actions %} workflow, in order to receive emails about build errors in your pull request, you must configure your workflow to run on the `pull_request` trigger. When you do this, we recommend that you skip any deploy steps if the workflow was triggered by the `pull_request` event. This will allow you to see any build errors without deploying the changes from your pull request to your site. For more information, see [AUTOTITLE](/actions/reference/workflows-and-actions/events-that-trigger-workflows#pull_request) and [AUTOTITLE](/actions/reference/workflows-and-actions/expressions). ## Viewing Jekyll build error messages in your pull request with a third-party CI service diff --git a/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md b/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md index f857090898fa..c24e3ddaa636 100644 --- a/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md +++ b/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md @@ -118,7 +118,7 @@ Before you can use Jekyll to create a {% data variables.product.prodname_pages % baseurl: /REPOSITORY-NAME/ # place folder name if the site is served in a subfolder ``` -1. Optionally, test your site locally. For more information, see [Testing your {% data variables.product.prodname_pages %} site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll). +1. Optionally, test your site locally. For more information, see [AUTOTITLE](/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll). 1. Add and commit your work. ```shell From 4250a7b9dc69d617fde5627d0184c80fefab7e36 Mon Sep 17 00:00:00 2001 From: Kevin Heis Date: Thu, 9 Jul 2026 06:42:06 -0700 Subject: [PATCH 11/17] Update redirected internal links in packages (#62116) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .../about-permissions-for-github-packages.md | 4 ++-- ...a-packages-access-control-and-visibility.md | 2 +- .../introduction-to-github-packages.md | 8 ++++---- .../publishing-a-package.md | 2 +- ...ample-workflows-for-publishing-a-package.md | 8 ++++---- ...installing-a-package-with-github-actions.md | 18 +++++++++--------- content/packages/quickstart.md | 4 ++-- ...tainer-registry-from-the-docker-registry.md | 6 +++--- .../working-with-the-container-registry.md | 2 +- .../working-with-the-gradle-registry.md | 2 +- .../working-with-the-npm-registry.md | 2 +- .../working-with-the-nuget-registry.md | 2 +- 12 files changed, 30 insertions(+), 30 deletions(-) diff --git a/content/packages/learn-github-packages/about-permissions-for-github-packages.md b/content/packages/learn-github-packages/about-permissions-for-github-packages.md index ab1da443ceef..fd7b29440ab2 100644 --- a/content/packages/learn-github-packages/about-permissions-for-github-packages.md +++ b/content/packages/learn-github-packages/about-permissions-for-github-packages.md @@ -84,7 +84,7 @@ When you create a {% data variables.product.prodname_actions %} workflow, you ca For more information, see:{% ifversion fpt or ghec %} * [AUTOTITLE](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility){% endif %} * [AUTOTITLE](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions) -* [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token) +* [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens) * [AUTOTITLE](/apps/oauth-apps/building-oauth-apps/scopes-for-oauth-apps#available-scopes) ## About repository transfers @@ -109,7 +109,7 @@ For more conceptual background on {% data variables.product.prodname_actions %} * To publish, install, delete, and restore packages associated with the workflow repository, use `GITHUB_TOKEN`. * To install packages associated with other private repositories that `GITHUB_TOKEN` can't access, use a {% data variables.product.pat_v1 %} -For more information about `GITHUB_TOKEN` used in {% data variables.product.prodname_actions %} workflows, see [AUTOTITLE](/actions/security-guides/automatic-token-authentication#using-the-github_token-in-a-workflow). +For more information about `GITHUB_TOKEN` used in {% data variables.product.prodname_actions %} workflows, see [AUTOTITLE](/actions/tutorials/authenticate-with-github_token#using-the-github_token-in-a-workflow). {% ifversion fpt or ghec %} diff --git a/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md b/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md index 2a43fb938dba..90beacd26273 100644 --- a/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md +++ b/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md @@ -124,7 +124,7 @@ Granting a repository access here also allows {% data variables.product.prodname > [!NOTE] > * Syncing your package with a repository {% data variables.package_registry.package-settings-actions-access-menu %} is different than connecting your package to a repository. For more information about linking a repository to your package, see [AUTOTITLE](/packages/learn-github-packages/connecting-a-repository-to-a-package). -> * You can choose to limit permissions to workflow jobs usings the `permissions` key and `packages` scope. For more information, see [AUTOTITLE](/actions/using-jobs/assigning-permissions-to-jobs). +> * You can choose to limit permissions to workflow jobs using the `permissions` key and `packages` scope. For more information, see [AUTOTITLE](/actions/tutorials/authenticate-with-github_token#modifying-the-permissions-for-the-githubtoken). > * {% data reusables.package_registry.public-forks-private-packages %} ### {% data variables.product.prodname_actions %} access for packages scoped to personal accounts diff --git a/content/packages/learn-github-packages/introduction-to-github-packages.md b/content/packages/learn-github-packages/introduction-to-github-packages.md index c53c8b2d99fa..4443d0882786 100644 --- a/content/packages/learn-github-packages/introduction-to-github-packages.md +++ b/content/packages/learn-github-packages/introduction-to-github-packages.md @@ -33,7 +33,7 @@ You can view a package's README, as well as metadata such as licensing, download {% ifversion ghes %} -For more information about the configuration of {% data variables.product.prodname_registry %} on {% data variables.product.prodname_ghe_server %}, see [AUTOTITLE](/admin/packages/getting-started-with-github-packages-for-your-enterprise). +For more information about the configuration of {% data variables.product.prodname_registry %} on {% data variables.product.prodname_ghe_server %}, see [AUTOTITLE](/admin/configuring-packages/getting-started-with-github-packages-for-your-enterprise). {% endif %} @@ -72,7 +72,7 @@ For more information, see [AUTOTITLE](/code-security/concepts/supply-chain-secur {% data reusables.billing.default-over-quota-behavior %} -For more information, see [AUTOTITLE](/billing/managing-billing-for-github-packages/about-billing-for-github-packages). +For more information, see [AUTOTITLE](/billing/concepts/product-billing/github-packages). {% endif %} @@ -95,7 +95,7 @@ For more information, see [AUTOTITLE](/billing/managing-billing-for-github-packa {% ifversion ghes %} > [!NOTE] -> When enabling the Docker registry, we highly recommend also enabling subdomain isolation. For more information, see [AUTOTITLE](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation). +> When enabling the Docker registry, we highly recommend also enabling subdomain isolation. For more information, see [AUTOTITLE](/admin/configuring-settings/hardening-security-for-your-enterprise/enabling-subdomain-isolation). {% endif %} @@ -126,7 +126,7 @@ When you use the GraphQL API to query and delete private packages, you must use For more information, see {% ifversion ghes %}[AUTOTITLE](/packages/learn-github-packages/deleting-and-restoring-a-package) and {% endif %}[AUTOTITLE](/graphql/guides/forming-calls-with-graphql). -You can configure webhooks to subscribe to package-related events, such as when a package is published or updated. For more information, see the [AUTOTITLE](/webhooks-and-events/webhooks/webhook-events-and-payloads#package). +You can configure webhooks to subscribe to package-related events, such as when a package is published or updated. For more information, see the [AUTOTITLE](/webhooks/webhook-events-and-payloads#package). ## Contacting support diff --git a/content/packages/learn-github-packages/publishing-a-package.md b/content/packages/learn-github-packages/publishing-a-package.md index 46fa271152fc..26b3d8eb0dbc 100644 --- a/content/packages/learn-github-packages/publishing-a-package.md +++ b/content/packages/learn-github-packages/publishing-a-package.md @@ -23,7 +23,7 @@ You can help people understand and use your package by providing a description a {% data reusables.package_registry.public-or-private-packages %} A repository can be connected to more than one package. To prevent confusion, make sure the README and description clearly provide information about each package. {% ifversion fpt or ghec %} -If a new version of a package fixes a security vulnerability, you should publish a security advisory in your repository. {% data variables.product.prodname_dotcom %} reviews each published security advisory and may use it to send {% data variables.product.prodname_dependabot_alerts %} to affected repositories. For more information, see [AUTOTITLE](/code-security/security-advisories/working-with-repository-security-advisories/about-repository-security-advisories). +If a new version of a package fixes a security vulnerability, you should publish a security advisory in your repository. {% data variables.product.prodname_dotcom %} reviews each published security advisory and may use it to send {% data variables.product.prodname_dependabot_alerts %} to affected repositories. For more information, see [AUTOTITLE](/code-security/concepts/vulnerability-reporting-and-management/repository-security-advisories). {% endif %} ## Publishing a package diff --git a/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md b/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md index 19859cfaef36..8f9f344650eb 100644 --- a/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md +++ b/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md @@ -14,7 +14,7 @@ category: You can find example workflows in [AUTOTITLE](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions) or in any of these {% data variables.product.prodname_actions %} guides: -* [Publishing Node.js packages](/actions/publishing-packages/publishing-nodejs-packages) -* [Publishing Docker images](/actions/publishing-packages/publishing-docker-images) -* [Publishing Java packages with Maven](/actions/publishing-packages/publishing-java-packages-with-maven) -* [Publishing Java packages with Gradle](/actions/publishing-packages/publishing-java-packages-with-gradle) +* [Publishing Node.js packages](/actions/tutorials/publish-packages/publish-nodejs-packages) +* [Publishing Docker images](/actions/tutorials/publish-packages/publish-docker-images) +* [Publishing Java packages with Maven](/actions/tutorials/publish-packages/publish-java-packages-with-maven) +* [Publishing Java packages with Gradle](/actions/tutorials/publish-packages/publish-java-packages-with-gradle) diff --git a/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md b/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md index c66a1ceba3e2..ab19cf2a142e 100644 --- a/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md +++ b/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md @@ -22,7 +22,7 @@ category: ## About {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %} -{% data reusables.repositories.about-github-actions %} {% data reusables.repositories.actions-ci-cd %} For more information, see [AUTOTITLE](/actions/learn-github-actions). +{% data reusables.repositories.about-github-actions %} {% data reusables.repositories.actions-ci-cd %} For more information, see [AUTOTITLE](/actions/how-tos/write-workflows). You can extend the CI and CD capabilities of your repository by publishing or installing packages as part of your workflow. @@ -36,9 +36,9 @@ Some {% data variables.product.prodname_registry %} registries support granular Some {% data variables.product.prodname_registry %} registries only support repository-scoped permissions, and do not support granular permissions. For a list of these registries, see [AUTOTITLE](/packages/learn-github-packages/about-permissions-for-github-packages#permissions-for-repository-scoped-packages). -If you want your workflow to access a {% data variables.product.prodname_registry %} registry that does not support granular permissions, then we recommend using the `GITHUB_TOKEN` that {% data variables.product.github %} automatically creates for your repository when you enable {% data variables.product.prodname_actions %}. You should set the permissions for this access token in the workflow file to grant read access for the `contents` scope and write access for the `packages` scope. For forks, the `GITHUB_TOKEN` is granted read access for the parent repository. For more information, see [AUTOTITLE](/actions/security-guides/automatic-token-authentication). +If you want your workflow to access a {% data variables.product.prodname_registry %} registry that does not support granular permissions, then we recommend using the `GITHUB_TOKEN` that {% data variables.product.github %} automatically creates for your repository when you enable {% data variables.product.prodname_actions %}. You should set the permissions for this access token in the workflow file to grant read access for the `contents` scope and write access for the `packages` scope. For forks, the `GITHUB_TOKEN` is granted read access for the parent repository. For more information, see [AUTOTITLE](/actions/tutorials/authenticate-with-github_token). -You can reference the `GITHUB_TOKEN` in your workflow file using the {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %} context. For more information, see [AUTOTITLE](/actions/security-guides/automatic-token-authentication). +You can reference the `GITHUB_TOKEN` in your workflow file using the {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %} context. For more information, see [AUTOTITLE](/actions/tutorials/authenticate-with-github_token). ## About permissions and package access @@ -46,11 +46,11 @@ You can reference the `GITHUB_TOKEN` in your workflow file using the {% raw %}`$ Registries that support granular permissions allow users to create and administer packages as free-standing resources at the organization level. Packages can be scoped to an organization or personal account and you can customize access to each of your packages separately from repository permissions. -All workflows accessing registries that support granular permissions should use the `GITHUB_TOKEN` instead of a {% data variables.product.pat_generic %}. For more information about security best practices, see [AUTOTITLE](/actions/security-guides/security-hardening-for-github-actions#using-secrets). +All workflows accessing registries that support granular permissions should use the `GITHUB_TOKEN` instead of a {% data variables.product.pat_generic %}. For more information about security best practices, see [AUTOTITLE](/actions/reference/security/secure-use#use-secrets-for-sensitive-information). ### Packages scoped to repositories -When you enable GitHub Actions, GitHub installs a GitHub App on your repository. The `GITHUB_TOKEN` secret is a GitHub App installation access token. You can use the installation access token to authenticate on behalf of the GitHub App installed on your repository. The token's permissions are limited to the repository that contains your workflow. For more information, see [AUTOTITLE](/actions/security-guides/automatic-token-authentication#about-the-github_token-secret). +When you enable GitHub Actions, GitHub installs a GitHub App on your repository. The `GITHUB_TOKEN` secret is a GitHub App installation access token. You can use the installation access token to authenticate on behalf of the GitHub App installed on your repository. The token's permissions are limited to the repository that contains your workflow. For more information, see [AUTOTITLE](/actions/tutorials/authenticate-with-github_token#about-the-github_token-secret). {% data variables.product.prodname_registry %} allows you to push and pull packages through the `GITHUB_TOKEN` available to a {% data variables.product.prodname_actions %} workflow. @@ -78,7 +78,7 @@ You can use {% data variables.product.prodname_actions %} to automatically publi {% data reusables.package_registry.actions-configuration %} -The following example demonstrates how you can use {% data variables.product.prodname_actions %} to build {% ifversion not fpt or ghec %}and test{% endif %} your app, and then automatically create a Docker image and publish it to {% data variables.product.prodname_registry %}. The relevant settings are explained in the code. For full details about each element in a workflow, see [AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions). +The following example demonstrates how you can use {% data variables.product.prodname_actions %} to build {% ifversion not fpt or ghec %}and test{% endif %} your app, and then automatically create a Docker image and publish it to {% data variables.product.prodname_registry %}. The relevant settings are explained in the code. For full details about each element in a workflow, see [AUTOTITLE](/actions/reference/workflows-and-actions/workflow-syntax). Create a new workflow file in your repository (such as `.github/workflows/deploy-image.yml`), and add the following YAML. @@ -180,7 +180,7 @@ A few minutes after the workflow has completed, the new package will be visible You can install packages as part of your CI flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to a pull request, the workflow resolves dependencies by downloading and installing packages hosted by {% data variables.product.prodname_registry %}. Then, the workflow can run CI tests that require the dependencies. -Installing packages hosted by {% data variables.product.prodname_registry %} through {% data variables.product.prodname_actions %} requires minimal configuration or additional authentication when you use the `GITHUB_TOKEN`.{% ifversion fpt or ghec %} Data transfer is also free when an action installs a package. For more information, see [AUTOTITLE](/billing/managing-billing-for-github-packages/about-billing-for-github-packages).{% endif %} +Installing packages hosted by {% data variables.product.prodname_registry %} through {% data variables.product.prodname_actions %} requires minimal configuration or additional authentication when you use the `GITHUB_TOKEN`.{% ifversion fpt or ghec %} Data transfer is also free when an action installs a package. For more information, see [AUTOTITLE](/billing/concepts/product-billing/github-packages).{% endif %} {% data reusables.package_registry.actions-configuration %} @@ -188,9 +188,9 @@ Installing packages hosted by {% data variables.product.prodname_registry %} thr {% data variables.product.prodname_registry %} supports the `GITHUB_TOKEN` for easy and secure authentication in your workflows. If you're using a registry that supports granular permissions, and your workflow is using a {% data variables.product.pat_generic %} to authenticate to the registry, then we highly recommend you update your workflow to use the `GITHUB_TOKEN`. -For more information about the `GITHUB_TOKEN`, see [AUTOTITLE](/actions/security-guides/automatic-token-authentication#using-the-github_token-in-a-workflow). +For more information about the `GITHUB_TOKEN`, see [AUTOTITLE](/actions/tutorials/authenticate-with-github_token#using-the-github_token-in-a-workflow). -Using the `GITHUB_TOKEN`, instead of a {% data variables.product.pat_v1 %} with the `repo` scope, increases the security of your repository as you don't need to use a long-lived {% data variables.product.pat_generic %} that offers unnecessary access to the repository where your workflow is run. For more information about security best practices, see [AUTOTITLE](/actions/security-guides/security-hardening-for-github-actions#using-secrets). +Using the `GITHUB_TOKEN`, instead of a {% data variables.product.pat_v1 %} with the `repo` scope, increases the security of your repository as you don't need to use a long-lived {% data variables.product.pat_generic %} that offers unnecessary access to the repository where your workflow is run. For more information about security best practices, see [AUTOTITLE](/actions/reference/security/secure-use#use-secrets-for-sensitive-information). 1. Navigate to your package landing page. {% data reusables.package_registry.package-settings-actions-access %} diff --git a/content/packages/quickstart.md b/content/packages/quickstart.md index 6ec1cfe3024a..bc24e3bbe605 100644 --- a/content/packages/quickstart.md +++ b/content/packages/quickstart.md @@ -125,7 +125,7 @@ If you use a {% data variables.enterprise.prodname_managed_user %}, you cannot p 1. The workflow that you created will run whenever a new release is created in your repository. If the tests pass, then the package will be published to {% data variables.product.prodname_registry %}. - To test this out, navigate to the **Code** tab in your repository and create a new release. For more information, see [Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release). + To test this out, navigate to the **Code** tab in your repository and create a new release. For more information, see [Managing releases in a repository](/repositories/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release). ## Viewing your published package @@ -146,5 +146,5 @@ The basic workflow you just added runs any time a new release is created in your Combining {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %} can help you automate nearly every aspect of your application development processes. Ready to get started? Here are some helpful resources for taking your next steps with {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %}: * [AUTOTITLE](/packages/learn-github-packages) for an in-depth tutorial on GitHub Packages -* [AUTOTITLE](/actions/learn-github-actions) for an in-depth tutorial on GitHub Actions +* [AUTOTITLE](/actions/how-tos/write-workflows) for an in-depth tutorial on GitHub Actions * [AUTOTITLE](/packages/working-with-a-github-packages-registry) for specific uses cases and examples diff --git a/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md b/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md index 47db9a72ba98..d6ffd9eb9aa5 100644 --- a/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md +++ b/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md @@ -28,7 +28,7 @@ category: {% ifversion ghes %} > [!NOTE] -> {% data reusables.package_registry.container-registry-ghes-migration-availability %} For more information about finding the version of {% data variables.product.prodname_ghe_server %} that you use, see [AUTOTITLE](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server). +> {% data reusables.package_registry.container-registry-ghes-migration-availability %} For more information about finding the version of {% data variables.product.prodname_ghe_server %} that you use, see [AUTOTITLE](/get-started/using-github-docs/about-versions-of-github-docs#github-enterprise-server). {% endif %} @@ -45,12 +45,12 @@ After migration, you'll no longer be able to use the GraphQL API to query for pa ## About billing for {% data variables.product.prodname_container_registry %} -For more information about billing for the {% data variables.product.prodname_container_registry %}, see [AUTOTITLE](/billing/managing-billing-for-github-packages/about-billing-for-github-packages). +For more information about billing for the {% data variables.product.prodname_container_registry %}, see [AUTOTITLE](/billing/concepts/product-billing/github-packages). {% else %} ## Further reading -* [AUTOTITLE](/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry) +* [AUTOTITLE](/admin/configuring-packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry) {% endif %} diff --git a/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md b/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md index 297761a2605b..e04a86dac9a9 100644 --- a/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md +++ b/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md @@ -29,7 +29,7 @@ category: {% ifversion ghes %} -To use the {% data variables.product.prodname_container_registry %} on {% data variables.product.prodname_ghe_server %}, your site administrator must first configure {% data variables.product.prodname_registry %} for your instance **and** enable subdomain isolation. For more information, see [AUTOTITLE](/admin/packages/getting-started-with-github-packages-for-your-enterprise) and [AUTOTITLE](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation). +To use the {% data variables.product.prodname_container_registry %} on {% data variables.product.prodname_ghe_server %}, your site administrator must first configure {% data variables.product.prodname_registry %} for your instance **and** enable subdomain isolation. For more information, see [AUTOTITLE](/admin/configuring-packages/getting-started-with-github-packages-for-your-enterprise) and [AUTOTITLE](/admin/configuring-settings/hardening-security-for-your-enterprise/enabling-subdomain-isolation). {% endif %} diff --git a/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md b/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md index ee01401ae263..53c6efbc2944 100644 --- a/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md +++ b/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md @@ -31,7 +31,7 @@ category: {% data reusables.package_registry.authenticate-packages %} -{% data reusables.package_registry.authenticate-packages-github-token %} For more information about using `GITHUB_TOKEN` with Gradle, see [AUTOTITLE](/actions/publishing-packages/publishing-java-packages-with-gradle#publishing-packages-to-github-packages). +{% data reusables.package_registry.authenticate-packages-github-token %} For more information about using `GITHUB_TOKEN` with Gradle, see [AUTOTITLE](/actions/tutorials/publish-packages/publish-java-packages-with-gradle#publishing-packages-to-github-packages). ### Authenticating with a {% data variables.product.pat_generic %} diff --git a/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md b/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md index 1b1e9d2afd8c..8a0f2fafc335 100644 --- a/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md +++ b/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md @@ -250,5 +250,5 @@ If your instance has subdomain isolation disabled: ## Using the official npm registry -{% data variables.product.prodname_registry %} allows you to access the official npm registry at `registry.npmjs.com`, if your {% data variables.product.prodname_ghe_server %} administrator has enabled this feature. For more information, see [Connecting to the official npm registry](/admin/packages/configuring-package-ecosystem-support-for-your-enterprise#connecting-to-the-official-npm-registry). +{% data variables.product.prodname_registry %} allows you to access the official npm registry at `registry.npmjs.com`, if your {% data variables.product.prodname_ghe_server %} administrator has enabled this feature. For more information, see [Connecting to the official npm registry](/admin/configuring-packages/configuring-package-ecosystem-support-for-your-enterprise#connecting-to-the-official-npm-registry). {% endif %} diff --git a/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md b/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md index 6dc9cf40302d..59327922b92b 100644 --- a/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md +++ b/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md @@ -142,7 +142,7 @@ If you specify a `RepositoryURL` in your project's _.csproj_ file, the published ### Publishing a package using a GitHub {% data variables.product.pat_generic %} as your API key -If you don't already have a {% data variables.product.pat_generic %} to use for your account on {% data variables.product.github %}, see [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token). +If you don't already have a {% data variables.product.pat_generic %} to use for your account on {% data variables.product.github %}, see [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens). 1. Create a new project. Replace `PROJECT_NAME` with the name you'd like to give the project. From 44442041dd7fe7047d74f324744ffaf4dd8f7946 Mon Sep 17 00:00:00 2001 From: Kevin Heis Date: Thu, 9 Jul 2026 06:42:13 -0700 Subject: [PATCH 12/17] Update redirected internal links in webhooks (#62113) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- content/webhooks/about-webhooks.md | 2 +- .../redelivering-webhooks.md | 2 +- .../testing-webhooks.md | 2 +- .../viewing-webhook-deliveries.md | 2 +- content/webhooks/types-of-webhooks.md | 2 +- ...ering-failed-deliveries-for-a-github-app-webhook.md | 4 ++-- ...ering-failed-deliveries-for-a-repository-webhook.md | 4 ++-- ...ng-failed-deliveries-for-an-organization-webhook.md | 4 ++-- .../best-practices-for-using-webhooks.md | 4 ++-- content/webhooks/using-webhooks/creating-webhooks.md | 10 +++++----- .../delivering-webhooks-to-private-systems.md | 2 +- content/webhooks/using-webhooks/disabling-webhooks.md | 2 +- content/webhooks/using-webhooks/editing-webhooks.md | 8 ++++---- .../handling-failed-webhook-deliveries.md | 10 +++++----- .../using-webhooks/handling-webhook-deliveries.md | 2 +- .../using-webhooks/validating-webhook-deliveries.md | 2 +- content/webhooks/webhook-events-and-payloads.md | 4 ++-- 17 files changed, 33 insertions(+), 33 deletions(-) diff --git a/content/webhooks/about-webhooks.md b/content/webhooks/about-webhooks.md index fd4e6bc33499..529850e5a60d 100644 --- a/content/webhooks/about-webhooks.md +++ b/content/webhooks/about-webhooks.md @@ -44,7 +44,7 @@ For example, you could subscribe your webhook to events that occur when code is You must create a webhook within a specific repository, organization, {% ifversion ghes or ghec %}{% data variables.product.prodname_enterprise %}, {% endif %} {% ifversion fpt or ghec %}{% data variables.product.prodname_marketplace %} account, {% endif %} {% ifversion fpt or ghec %}{% data variables.product.prodname_sponsors %} account, {% endif %} or {% data variables.product.prodname_github_app %}. The webhook can only access resources that are available in the repository, organization, {% ifversion ghes or ghec %}{% data variables.product.prodname_enterprise %}, {% endif %} {% ifversion fpt or ghec %}{% data variables.product.prodname_marketplace %} account, {% endif %} {% ifversion fpt or ghec %}{% data variables.product.prodname_sponsors %} account, {% endif %} or {% data variables.product.prodname_github_app %} where it is installed. For more information, see [AUTOTITLE](/webhooks/types-of-webhooks). -For more information about creating webhooks, see [AUTOTITLE](/webhooks/using-webhooks/creating-webhooks). For more information about the types of events you can subscribe to, see [AUTOTITLE](/webhooks/webhook-events-and-payloads). For more information about configuring your server to take an action in response to a payload delivery, see [AUTOTITLE](/webhooks/using-webhooks/configuring-your-server-to-receive-payloads). +For more information about creating webhooks, see [AUTOTITLE](/webhooks/using-webhooks/creating-webhooks). For more information about the types of events you can subscribe to, see [AUTOTITLE](/webhooks/webhook-events-and-payloads). For more information about configuring your server to take an action in response to a payload delivery, see [AUTOTITLE](/webhooks/using-webhooks/handling-webhook-deliveries). {% data reusables.webhooks.webhooks-ipv6 %} diff --git a/content/webhooks/testing-and-troubleshooting-webhooks/redelivering-webhooks.md b/content/webhooks/testing-and-troubleshooting-webhooks/redelivering-webhooks.md index 6ae463e4fada..9fd6350daaaf 100644 --- a/content/webhooks/testing-and-troubleshooting-webhooks/redelivering-webhooks.md +++ b/content/webhooks/testing-and-troubleshooting-webhooks/redelivering-webhooks.md @@ -18,7 +18,7 @@ You may want to redeliver a webhook to help you test your application or to reco Only people with admin access to a repository can redeliver webhooks in that repository. -You can use the {% data variables.product.company_short %} web interface or the REST API to redeliver webhooks for a repository. For more information about using the REST API to redeliver webhooks, see [AUTOTITLE](/rest/webhooks/repo-deliveries). +You can use the {% data variables.product.company_short %} web interface or the REST API to redeliver webhooks for a repository. For more information about using the REST API to redeliver webhooks, see [AUTOTITLE](/rest/repos/webhooks). {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} diff --git a/content/webhooks/testing-and-troubleshooting-webhooks/testing-webhooks.md b/content/webhooks/testing-and-troubleshooting-webhooks/testing-webhooks.md index ad6323f9164a..f3c0788e0f4f 100644 --- a/content/webhooks/testing-and-troubleshooting-webhooks/testing-webhooks.md +++ b/content/webhooks/testing-and-troubleshooting-webhooks/testing-webhooks.md @@ -32,7 +32,7 @@ You can trigger a webhook event and verify that {% data variables.product.compan You can also redeliver a previous webhook delivery. For more information, see [AUTOTITLE](/webhooks/testing-and-troubleshooting-webhooks/redelivering-webhooks). - If you are using an organization or repository webhook, you can also use the REST API to trigger the `ping` event for your webhook. If you are using a repository webhook and your webhook is subscribed to the `push` event, you can use the REST API to trigger a test `push` event for your webhook. For more information, see [AUTOTITLE](/rest/webhooks/repos) and [AUTOTITLE](/rest/orgs/webhooks). + If you are using an organization or repository webhook, you can also use the REST API to trigger the `ping` event for your webhook. If you are using a repository webhook and your webhook is subscribed to the `push` event, you can use the REST API to trigger a test `push` event for your webhook. For more information, see [AUTOTITLE](/rest/repos/webhooks) and [AUTOTITLE](/rest/orgs/webhooks). 1. Check {% data variables.product.company_short %} to verify that a webhook delivery was sent. For information about how to do this for each webhook type, see [AUTOTITLE](/webhooks/testing-and-troubleshooting-webhooks/viewing-webhook-deliveries). diff --git a/content/webhooks/testing-and-troubleshooting-webhooks/viewing-webhook-deliveries.md b/content/webhooks/testing-and-troubleshooting-webhooks/viewing-webhook-deliveries.md index acecd2893f87..5206896f4055 100644 --- a/content/webhooks/testing-and-troubleshooting-webhooks/viewing-webhook-deliveries.md +++ b/content/webhooks/testing-and-troubleshooting-webhooks/viewing-webhook-deliveries.md @@ -26,7 +26,7 @@ You can also redeliver recent webhook deliveries. For more information, see [AUT Only people with admin access to a repository can view deliveries for webhooks in that repository. -You can use the {% data variables.product.company_short %} web interface or the REST API to view recent webhook deliveries for a repository. For more information about using the REST API to view recent deliveries, see [AUTOTITLE](/rest/webhooks/repo-deliveries). +You can use the {% data variables.product.company_short %} web interface or the REST API to view recent webhook deliveries for a repository. For more information about using the REST API to view recent deliveries, see [AUTOTITLE](/rest/repos/webhooks). {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} diff --git a/content/webhooks/types-of-webhooks.md b/content/webhooks/types-of-webhooks.md index d34e68c4c183..00c023248327 100644 --- a/content/webhooks/types-of-webhooks.md +++ b/content/webhooks/types-of-webhooks.md @@ -31,7 +31,7 @@ You can create webhooks in a repository to subscribe to events that occur in tha You can create multiple webhooks in a single repository. However, you can only create up to {% ifversion ghes %}250{% else %}20{% endif %} webhooks that subscribe to each individual event type. For example, in a single repository you could only create up to {% ifversion ghes %}250{% else %}20{% endif %} different webhooks that each subscribe to the `push` event. -You can use the {% data variables.product.github %} web interface or the REST API to manage repository webhooks. For more information, see [AUTOTITLE](/webhooks/using-webhooks/creating-webhooks#creating-a-repository-webhook), [AUTOTITLE](/webhooks/using-webhooks/editing-webhooks#editing-a-repository-webhook), and [AUTOTITLE](/webhooks/using-webhooks/disabling-webhooks#disabling-a-repository-webhook). For more information about using the REST API to manage repository webhooks, see [AUTOTITLE](/rest/webhooks). +You can use the {% data variables.product.github %} web interface or the REST API to manage repository webhooks. For more information, see [AUTOTITLE](/webhooks/using-webhooks/creating-webhooks#creating-a-repository-webhook), [AUTOTITLE](/webhooks/using-webhooks/editing-webhooks#editing-a-repository-webhook), and [AUTOTITLE](/webhooks/using-webhooks/disabling-webhooks#disabling-a-repository-webhook). For more information about using the REST API to manage repository webhooks, see [AUTOTITLE](/rest/repos/webhooks). ## Organization webhooks diff --git a/content/webhooks/using-webhooks/automatically-redelivering-failed-deliveries-for-a-github-app-webhook.md b/content/webhooks/using-webhooks/automatically-redelivering-failed-deliveries-for-a-github-app-webhook.md index 641474fabfb7..45907e7d8666 100644 --- a/content/webhooks/using-webhooks/automatically-redelivering-failed-deliveries-for-a-github-app-webhook.md +++ b/content/webhooks/using-webhooks/automatically-redelivering-failed-deliveries-for-a-github-app-webhook.md @@ -32,7 +32,7 @@ The endpoints to find and redeliver failed webhooks require a JSON web token, wh The endpoints to fetch and update the value of environment variables require a {% data variables.product.pat_generic %}, {% data variables.product.prodname_github_app %} installation access token, or {% data variables.product.prodname_github_app %} user access token. This example uses a {% data variables.product.pat_generic %}. If your {% data variables.product.prodname_github_app %} is installed on the repository where this workflow will run and has permission to write repository variables, you can modify this example to create an installation access token during the {% data variables.product.prodname_actions %} workflow instead of using a {% data variables.product.pat_generic %}. For more information, see [AUTOTITLE](/apps/creating-github-apps/authenticating-with-a-github-app/making-authenticated-api-requests-with-a-github-app-in-a-github-actions-workflow). 1. Find the app ID for your {% data variables.product.prodname_github_app %}. You can find the app ID on the settings page for your app. The app ID is different from the client ID. For more information about navigating to the settings page for your {% data variables.product.prodname_github_app %}, see [AUTOTITLE](/apps/maintaining-github-apps/modifying-a-github-app-registration#navigating-to-your-github-app-settings). -1. Store the app ID from the previous step as a {% data variables.product.prodname_actions %} secret in the repository where you want the workflow to run. For more information about storing secrets, see [AUTOTITLE](/actions/security-guides/encrypted-secrets). +1. Store the app ID from the previous step as a {% data variables.product.prodname_actions %} secret in the repository where you want the workflow to run. For more information about storing secrets, see [AUTOTITLE](/actions/how-tos/write-workflows/choose-what-workflows-do/use-secrets). 1. Generate a private key for your app. For more information about generating a private key, see [AUTOTITLE](/apps/creating-github-apps/authenticating-with-a-github-app/managing-private-keys-for-github-apps). 1. Store the private key, including `-----BEGIN RSA PRIVATE KEY-----` and `-----END RSA PRIVATE KEY-----`, from the previous step as a {% data variables.product.prodname_actions %} secret in the repository where you want the workflow to run. 1. Create a {% data variables.product.pat_generic %} with the following access. For more information, see [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens). @@ -329,7 +329,7 @@ async function updateVariable({ ## Testing the script -You can manually trigger your workflow to test the script. For more information, see [AUTOTITLE](/actions/using-workflows/manually-running-a-workflow) and [AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs). +You can manually trigger your workflow to test the script. For more information, see [AUTOTITLE](/actions/how-tos/manage-workflow-runs/manually-run-a-workflow) and [AUTOTITLE](/actions/how-tos/monitor-workflows/use-workflow-run-logs). ## Alternative methods diff --git a/content/webhooks/using-webhooks/automatically-redelivering-failed-deliveries-for-a-repository-webhook.md b/content/webhooks/using-webhooks/automatically-redelivering-failed-deliveries-for-a-repository-webhook.md index df94c434f684..950960b9703f 100644 --- a/content/webhooks/using-webhooks/automatically-redelivering-failed-deliveries-for-a-repository-webhook.md +++ b/content/webhooks/using-webhooks/automatically-redelivering-failed-deliveries-for-a-repository-webhook.md @@ -36,7 +36,7 @@ The built in `GITHUB_TOKEN` does not have sufficient permissions to redeliver we * Write access to the repository webhooks permission * Write access to the repository variables permission * For a {% data variables.product.pat_v1 %}, grant the token the `repo` scope. -1. Store your {% data variables.product.pat_generic %} as a {% data variables.product.prodname_actions %} secret in the repository where you want the workflow to run. For more information, see [AUTOTITLE](/actions/security-guides/encrypted-secrets). +1. Store your {% data variables.product.pat_generic %} as a {% data variables.product.prodname_actions %} secret in the repository where you want the workflow to run. For more information, see [AUTOTITLE](/actions/how-tos/write-workflows/choose-what-workflows-do/use-secrets). ## Adding a workflow that will run the script @@ -347,7 +347,7 @@ async function updateVariable({ ## Testing the script -You can manually trigger your workflow to test the script. For more information, see [AUTOTITLE](/actions/using-workflows/manually-running-a-workflow) and [AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs). +You can manually trigger your workflow to test the script. For more information, see [AUTOTITLE](/actions/how-tos/manage-workflow-runs/manually-run-a-workflow) and [AUTOTITLE](/actions/how-tos/monitor-workflows/use-workflow-run-logs). ## Alternative methods diff --git a/content/webhooks/using-webhooks/automatically-redelivering-failed-deliveries-for-an-organization-webhook.md b/content/webhooks/using-webhooks/automatically-redelivering-failed-deliveries-for-an-organization-webhook.md index e84bee84a45b..c09fd35332ca 100644 --- a/content/webhooks/using-webhooks/automatically-redelivering-failed-deliveries-for-an-organization-webhook.md +++ b/content/webhooks/using-webhooks/automatically-redelivering-failed-deliveries-for-an-organization-webhook.md @@ -36,7 +36,7 @@ The built in `GITHUB_TOKEN` does not have sufficient permissions to redeliver we * Grant the token write access to the organization webhooks permission * Grant the token write access to the repository variables permission * For a {% data variables.product.pat_v1 %}, grant the token the `admin:org_hook` and `repo` scope. -1. Store your {% data variables.product.pat_generic %} as a {% data variables.product.prodname_actions %} secret in the repository where you want the workflow to run. For more information, see [AUTOTITLE](/actions/security-guides/encrypted-secrets). +1. Store your {% data variables.product.pat_generic %} as a {% data variables.product.prodname_actions %} secret in the repository where you want the workflow to run. For more information, see [AUTOTITLE](/actions/how-tos/write-workflows/choose-what-workflows-do/use-secrets). ## Adding a workflow that will run the script @@ -338,7 +338,7 @@ async function updateVariable({ ## Testing the script -You can manually trigger your workflow to test the script. For more information, see [AUTOTITLE](/actions/using-workflows/manually-running-a-workflow) and [AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs). +You can manually trigger your workflow to test the script. For more information, see [AUTOTITLE](/actions/how-tos/manage-workflow-runs/manually-run-a-workflow) and [AUTOTITLE](/actions/how-tos/monitor-workflows/use-workflow-run-logs). ## Alternative methods diff --git a/content/webhooks/using-webhooks/best-practices-for-using-webhooks.md b/content/webhooks/using-webhooks/best-practices-for-using-webhooks.md index 2f83bc5923ee..4d7ea7ec8639 100644 --- a/content/webhooks/using-webhooks/best-practices-for-using-webhooks.md +++ b/content/webhooks/using-webhooks/best-practices-for-using-webhooks.md @@ -12,7 +12,7 @@ category: ## Subscribe to the minimum number of events -You should only subscribe to the webhook events that you need. This will reduce the amount of work your server needs to do. For more information about subscribing to events, see [AUTOTITLE](/webhooks/creating-webhooks) and [AUTOTITLE](/webhooks/using-webhooks/editing-webhooks). +You should only subscribe to the webhook events that you need. This will reduce the amount of work your server needs to do. For more information about subscribing to events, see [AUTOTITLE](/webhooks/using-webhooks/creating-webhooks) and [AUTOTITLE](/webhooks/using-webhooks/editing-webhooks). ## Use a webhook secret @@ -61,5 +61,5 @@ In a replay attack, a bad actor intercepts a webhook delivery and re-sends the d ## Further reading -* [AUTOTITLE](/rest/guides/best-practices-for-integrators) +* [AUTOTITLE](/rest/using-the-rest-api/best-practices-for-using-the-rest-api) * [AUTOTITLE](/apps/creating-github-apps/about-creating-github-apps/best-practices-for-creating-a-github-app) diff --git a/content/webhooks/using-webhooks/creating-webhooks.md b/content/webhooks/using-webhooks/creating-webhooks.md index 65e992c25a0b..870d04d7952e 100644 --- a/content/webhooks/using-webhooks/creating-webhooks.md +++ b/content/webhooks/using-webhooks/creating-webhooks.md @@ -29,7 +29,7 @@ For a complete list of webhook events, see [AUTOTITLE](/webhooks/webhook-events- You can create a webhook to subscribe to events that occur in a specific repository. You must be a repository owner or have admin access in the repository to create webhooks in that repository. -You can use the {% data variables.product.github %} web interface or the REST API to create a repository webhook. For more information about using the REST API to create a repository webhook, see [AUTOTITLE](/rest/webhooks/repos#create-a-repository-webhook). +You can use the {% data variables.product.github %} web interface or the REST API to create a repository webhook. For more information about using the REST API to create a repository webhook, see [AUTOTITLE](/rest/repos/webhooks#create-a-repository-webhook). {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -112,7 +112,7 @@ After you create a new webhook, {% data variables.product.github %} will send yo ## Creating a {% data variables.product.prodname_sponsors %} webhook -You can create a webhook to subscribe to events relating to your sponsorships. Only the owner of the sponsored account can create sponsorship webhooks for that account. For more information about the event that a sponsorship webhook is subscribed to, see the [`sponsorship` webhook event](/webhooks-and-events/webhooks/webhook-events-and-payloads#sponsorship). +You can create a webhook to subscribe to events relating to your sponsorships. Only the owner of the sponsored account can create sponsorship webhooks for that account. For more information about the event that a sponsorship webhook is subscribed to, see the [`sponsorship` webhook event](/webhooks/webhook-events-and-payloads#sponsorship). 1. In the upper-right corner of any page, click your profile picture, then click **Your sponsors**. 1. Next to the account you want to create a webhook for, click **Dashboard**. @@ -127,7 +127,7 @@ You can create a webhook to subscribe to events relating to your sponsorships. O ## Creating webhooks for a {% data variables.product.prodname_github_app %} -The owner of a {% data variables.product.prodname_github_app %} can subscribe the app to webhook events to receive notifications whenever certain events occur. If the app owner has designated any app managers for a {% data variables.product.prodname_github_app %}, the app managers can also subscribe the app to webhook events. For more information, see [AUTOTITLE](/apps/creating-github-apps/creating-github-apps/using-webhooks-with-github-apps). +The owner of a {% data variables.product.prodname_github_app %} can subscribe the app to webhook events to receive notifications whenever certain events occur. If the app owner has designated any app managers for a {% data variables.product.prodname_github_app %}, the app managers can also subscribe the app to webhook events. For more information, see [AUTOTITLE](/apps/creating-github-apps/registering-a-github-app/using-webhooks-with-github-apps). Each {% data variables.product.prodname_github_app %} has one webhook. You can configure the webhook when you register a {% data variables.product.prodname_github_app %}, or you can edit the webhook configuration for an existing {% data variables.product.prodname_github_app %} registration. @@ -140,12 +140,12 @@ To configure a webhook for an existing {% data variables.product.prodname_github 1. Next to the {% data variables.product.prodname_github_app %} that you want to configure the webhook for, click **Edit**. 1. Under "Webhook," select **Active**. 1. Under "Webhook URL", type the URL where you'd like to receive payloads. -1. Optionally, under "Webhook secret", type a string to use as a `secret` key. You should choose a random string of text with high entropy. You can use the webhook secret to limit incoming requests to only those originating from {% data variables.product.github %}. For more information, see [AUTOTITLE](/webhooks/using-webhooks/securing-your-webhooks). +1. Optionally, under "Webhook secret", type a string to use as a `secret` key. You should choose a random string of text with high entropy. You can use the webhook secret to limit incoming requests to only those originating from {% data variables.product.github %}. For more information, see [AUTOTITLE](/webhooks/using-webhooks/validating-webhook-deliveries). 1. Click **Save changes**. 1. In the sidebar, click **Permissions & events**. 1. {% data reusables.apps.webhooks-and-apps %} - Under the sections "Repository permissions," "Organization permissions," and "Account permissions," select the permissions that are required for the events your app will subscribe to. For more information, see [AUTOTITLE](/apps/creating-github-apps/creating-github-apps/choosing-permissions-for-a-github-app). For more information about things to consider when changing the permissions, see [Modifying a {% data variables.product.prodname_github_app %} registration](/apps/maintaining-github-apps/modifying-a-github-app-registration#changing-the-permissions-of-a-github-app). + Under the sections "Repository permissions," "Organization permissions," and "Account permissions," select the permissions that are required for the events your app will subscribe to. For more information, see [AUTOTITLE](/apps/creating-github-apps/registering-a-github-app/choosing-permissions-for-a-github-app). For more information about things to consider when changing the permissions, see [Modifying a {% data variables.product.prodname_github_app %} registration](/apps/maintaining-github-apps/modifying-a-github-app-registration#changing-the-permissions-of-a-github-app). 1. Under "Subscribe to Events," select the webhook events you would like your {% data variables.product.prodname_github_app %} to receive. 1. Click **Save changes**. diff --git a/content/webhooks/using-webhooks/delivering-webhooks-to-private-systems.md b/content/webhooks/using-webhooks/delivering-webhooks-to-private-systems.md index 0643c017e0a6..ee5f1f5be11a 100644 --- a/content/webhooks/using-webhooks/delivering-webhooks-to-private-systems.md +++ b/content/webhooks/using-webhooks/delivering-webhooks-to-private-systems.md @@ -34,6 +34,6 @@ The [`/meta` endpoint](/rest/meta/meta#get-github-meta-information) returns a JS ### Validating webhook payloads -If your webhook is configured with a secret token, {% data variables.product.github %} will include a cryptographic hash of each webhook payload. You should use this hash to validate the payload received from {% data variables.product.github %} before any action is taken by your private system. For more information, see [AUTOTITLE](/webhooks-and-events/webhooks/securing-your-webhooks). +If your webhook is configured with a secret token, {% data variables.product.github %} will include a cryptographic hash of each webhook payload. You should use this hash to validate the payload received from {% data variables.product.github %} before any action is taken by your private system. For more information, see [AUTOTITLE](/webhooks/using-webhooks/validating-webhook-deliveries). You can implement payload validation either on the reverse proxy or on your private system. diff --git a/content/webhooks/using-webhooks/disabling-webhooks.md b/content/webhooks/using-webhooks/disabling-webhooks.md index 73e2f33b7d73..f11fbeff36a2 100644 --- a/content/webhooks/using-webhooks/disabling-webhooks.md +++ b/content/webhooks/using-webhooks/disabling-webhooks.md @@ -26,7 +26,7 @@ For more information, see [AUTOTITLE](/webhooks/about-webhooks) and [AUTOTITLE]( To disable a repository webhook, you can deactivate or delete it. You must be a repository owner, or have admin access in the repository, to disable webhooks. -You can use the {% data variables.product.github %} web interface or the REST API to delete a webhook for a repository. For more information about using the REST API to delete a repository webhook, see [AUTOTITLE](/rest/webhooks/repos#delete-a-repository-webhook). +You can use the {% data variables.product.github %} web interface or the REST API to delete a webhook for a repository. For more information about using the REST API to delete a repository webhook, see [AUTOTITLE](/rest/repos/webhooks#delete-a-repository-webhook). {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} diff --git a/content/webhooks/using-webhooks/editing-webhooks.md b/content/webhooks/using-webhooks/editing-webhooks.md index a3d07f52153a..94e655f404aa 100644 --- a/content/webhooks/using-webhooks/editing-webhooks.md +++ b/content/webhooks/using-webhooks/editing-webhooks.md @@ -18,7 +18,7 @@ You can edit a webhook to change any of the settings that were selected when the You can edit a webhook that was created in a specific repository. You must be a repository owner or have admin access in the repository to edit webhooks in that repository. -You can use the {% data variables.product.github %} web interface or the REST API to edit a repository webhook. For more information about using the REST API to edit a repository webhook, see [AUTOTITLE](/rest/webhooks/repos#update-a-repository-webhook). +You can use the {% data variables.product.github %} web interface or the REST API to edit a repository webhook. For more information about using the REST API to edit a repository webhook, see [AUTOTITLE](/rest/repos/webhooks#update-a-repository-webhook). {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -65,7 +65,7 @@ You can use the {% data variables.product.company_short %} web interface or the ## Editing a {% data variables.product.prodname_marketplace %} webhook -You can edit a webhook that was created for an app that you published in {% data variables.product.prodname_marketplace %}. Only the owner of the app, or an app manager for the app, can edit a {% data variables.product.prodname_marketplace %} webhook. For more information, see [AUTOTITLE](/apps/publishing-apps-to-github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api). +You can edit a webhook that was created for an app that you published in {% data variables.product.prodname_marketplace %}. Only the owner of the app, or an app manager for the app, can edit a {% data variables.product.prodname_marketplace %} webhook. For more information, see [AUTOTITLE](/apps/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api). 1. Navigate to your [{% data variables.product.prodname_marketplace %} listing page](https://github.com/marketplace/manage). 1. Next to the {% data variables.product.prodname_marketplace %} listing that you want to view webhook deliveries for, click **Manage listing**. @@ -90,7 +90,7 @@ You can edit a webhook that was created for a {% data variables.product.prodname Each {% data variables.product.prodname_github_app %} has one webhook. You cannot delete the webhook, but you can activate or deactivate the webhook, change the webhook events that the webhook subscribes to, or make changes to other basic settings for the webhook. -The owner of a {% data variables.product.prodname_github_app %} can edit the webhook configuration for the app. If the app owner has designated any app managers for a {% data variables.product.prodname_github_app %}, the app managers can also edit the webhook configuration. For more information, see [AUTOTITLE](/apps/creating-github-apps/creating-github-apps/using-webhooks-with-github-apps). +The owner of a {% data variables.product.prodname_github_app %} can edit the webhook configuration for the app. If the app owner has designated any app managers for a {% data variables.product.prodname_github_app %}, the app managers can also edit the webhook configuration. For more information, see [AUTOTITLE](/apps/creating-github-apps/registering-a-github-app/using-webhooks-with-github-apps). {% data reusables.apps.settings-step %} {% data reusables.user-settings.developer_settings %} @@ -103,7 +103,7 @@ The owner of a {% data variables.product.prodname_github_app %} can edit the web 1. In the sidebar, click **Permissions & events**. 1. {% data reusables.apps.webhooks-and-apps %} - Under the sections "Repository permissions," "Organization permissions," and "Account permissions," select the permissions that are required for the events your app will subscribe to. For more information, see [AUTOTITLE](/apps/creating-github-apps/creating-github-apps/choosing-permissions-for-a-github-app). For more information about things to consider when changing the permissions, see [Modifying a {% data variables.product.prodname_github_app %} registration](/apps/maintaining-github-apps/modifying-a-github-app-registration#changing-the-permissions-of-a-github-app). + Under the sections "Repository permissions," "Organization permissions," and "Account permissions," select the permissions that are required for the events your app will subscribe to. For more information, see [AUTOTITLE](/apps/creating-github-apps/registering-a-github-app/choosing-permissions-for-a-github-app). For more information about things to consider when changing the permissions, see [Modifying a {% data variables.product.prodname_github_app %} registration](/apps/maintaining-github-apps/modifying-a-github-app-registration#changing-the-permissions-of-a-github-app). 1. Under "Subscribe to Events," select the webhook events you would like your {% data variables.product.prodname_github_app %} to receive. 1. Click **Save changes**. diff --git a/content/webhooks/using-webhooks/handling-failed-webhook-deliveries.md b/content/webhooks/using-webhooks/handling-failed-webhook-deliveries.md index bd278efe4fa9..0e04c366d803 100644 --- a/content/webhooks/using-webhooks/handling-failed-webhook-deliveries.md +++ b/content/webhooks/using-webhooks/handling-failed-webhook-deliveries.md @@ -23,17 +23,17 @@ You can manually redeliver failed deliveries. For more information, see [AUTOTIT You can also write a script that checks for failed deliveries and attempts to redeliver any that failed. Your script should run on a schedule and do the following: -1. Use the {% data variables.product.company_short %} REST API to fetch data about any webhook deliveries that were attempted since the last time that your script ran. For more information, see [AUTOTITLE](/rest/webhooks/repo-deliveries#list-deliveries-for-a-repository-webhook), [AUTOTITLE](/rest/orgs/webhooks#list-deliveries-for-an-organization-webhook), and [AUTOTITLE](/rest/apps/webhooks#list-deliveries-for-an-app-webhook). +1. Use the {% data variables.product.company_short %} REST API to fetch data about any webhook deliveries that were attempted since the last time that your script ran. For more information, see [AUTOTITLE](/rest/repos/webhooks#list-deliveries-for-a-repository-webhook), [AUTOTITLE](/rest/orgs/webhooks#list-deliveries-for-an-organization-webhook), and [AUTOTITLE](/rest/apps/webhooks#list-deliveries-for-an-app-webhook). {% ifversion fpt %}There are no API endpoints to get data about {% data variables.product.prodname_marketplace %} webhooks or {% data variables.product.prodname_sponsors %} webhooks.{% endif %}{% ifversion ghec %}There are no API endpoints to get data about {% data variables.product.prodname_marketplace %} webhooks, {% data variables.product.prodname_sponsors %} webhooks, or global webhooks.{% endif %}{% ifversion ghes %}There are no API endpoints to get data about global webhook deliveries.{% endif %} 1. Look at the fetched data to see if any deliveries failed. The data for a failed delivery will have a `status` value that is not `OK`. -1. Use the {% data variables.product.company_short %} REST API to redeliver any deliveries that failed. For more information, see [AUTOTITLE](/rest/webhooks/repo-deliveries#redeliver-a-delivery-for-a-repository-webhook), [AUTOTITLE](/rest/orgs/webhooks#redeliver-a-delivery-for-an-organization-webhook), and [AUTOTITLE](/rest/apps/webhooks#redeliver-a-delivery-for-an-app-webhook). +1. Use the {% data variables.product.company_short %} REST API to redeliver any deliveries that failed. For more information, see [AUTOTITLE](/rest/repos/webhooks#redeliver-a-delivery-for-a-repository-webhook), [AUTOTITLE](/rest/orgs/webhooks#redeliver-a-delivery-for-an-organization-webhook), and [AUTOTITLE](/rest/apps/webhooks#redeliver-a-delivery-for-an-app-webhook). For example scripts, see: -* [AUTOTITLE](/webhooks/using-webhooks/creating-a-script-to-automatically-redeliver-failed-deliveries-for-a-repository-webhook) -* [AUTOTITLE](/webhooks/using-webhooks/creating-a-script-to-automatically-redeliver-failed-deliveries-for-an-organization-webhook) -* [AUTOTITLE](/webhooks/using-webhooks/creating-a-script-to-automatically-redeliver-failed-deliveries-for-a-github-app-webhook) +* [AUTOTITLE](/webhooks/using-webhooks/automatically-redelivering-failed-deliveries-for-a-repository-webhook) +* [AUTOTITLE](/webhooks/using-webhooks/automatically-redelivering-failed-deliveries-for-an-organization-webhook) +* [AUTOTITLE](/webhooks/using-webhooks/automatically-redelivering-failed-deliveries-for-a-github-app-webhook) If a webhook delivery fails repeatedly, you should investigate the cause. Each failed delivery will give a reason for failure. For more information, see [AUTOTITLE](/webhooks/testing-and-troubleshooting-webhooks/troubleshooting-webhooks). diff --git a/content/webhooks/using-webhooks/handling-webhook-deliveries.md b/content/webhooks/using-webhooks/handling-webhook-deliveries.md index 540a07695f15..a86befb45af7 100644 --- a/content/webhooks/using-webhooks/handling-webhook-deliveries.md +++ b/content/webhooks/using-webhooks/handling-webhook-deliveries.md @@ -306,7 +306,7 @@ This article gave basic examples that print a message when a webhook delivery is ### Verify that the delivery is from {% data variables.product.company_short %} -In your code that handles webhook deliveries, you should validate that the delivery is from {% data variables.product.company_short %} before processing the delivery further. For more information, see [AUTOTITLE](/webhooks/using-webhooks/securing-your-webhooks). +In your code that handles webhook deliveries, you should validate that the delivery is from {% data variables.product.company_short %} before processing the delivery further. For more information, see [AUTOTITLE](/webhooks/using-webhooks/validating-webhook-deliveries). ### Deploy your code to a server diff --git a/content/webhooks/using-webhooks/validating-webhook-deliveries.md b/content/webhooks/using-webhooks/validating-webhook-deliveries.md index 1b73ae122e53..bf8e6694ea59 100644 --- a/content/webhooks/using-webhooks/validating-webhook-deliveries.md +++ b/content/webhooks/using-webhooks/validating-webhook-deliveries.md @@ -37,7 +37,7 @@ You can create a new webhook with a secret token, or you can add a secret token ## Securely storing the secret token -After creating a secret token, you should store it in a secure location that your server can access. Never hardcode a token into an application or push a token to any repository. For more information about how to use authentication credentials securely in your code, see [AUTOTITLE](/rest/overview/keeping-your-api-credentials-secure#use-authentication-credentials-securely-in-your-code). +After creating a secret token, you should store it in a secure location that your server can access. Never hardcode a token into an application or push a token to any repository. For more information about how to use authentication credentials securely in your code, see [AUTOTITLE](/rest/authentication/keeping-your-api-credentials-secure#use-authentication-credentials-securely-in-your-code). ## Validating webhook deliveries diff --git a/content/webhooks/webhook-events-and-payloads.md b/content/webhooks/webhook-events-and-payloads.md index 0c7034c56aab..7d24ab24d484 100644 --- a/content/webhooks/webhook-events-and-payloads.md +++ b/content/webhooks/webhook-events-and-payloads.md @@ -21,7 +21,7 @@ category: ## About webhook events and payloads -You can create webhooks that subscribe to the events listed on this page. To limit the number of HTTP requests to your server, you should only subscribe to the specific events that you plan on handling. For more information, see [AUTOTITLE](/webhooks/creating-webhooks). +You can create webhooks that subscribe to the events listed on this page. To limit the number of HTTP requests to your server, you should only subscribe to the specific events that you plan on handling. For more information, see [AUTOTITLE](/webhooks/using-webhooks/creating-webhooks). Each webhook event on this page includes a description of the webhook properties for that event. If the event has multiple actions, the properties corresponding to each action are included. @@ -41,7 +41,7 @@ HTTP POST payloads that are delivered to your webhook's configured URL endpoint * `X-GitHub-Enterprise-Version`: The version of the {% data variables.product.prodname_ghe_server %} instance that sent the HTTP POST payload. * `X-GitHub-Enterprise-Host`: The hostname of the {% data variables.product.prodname_ghe_server %} instance that sent the HTTP POST payload.{% endif %} * `X-Hub-Signature`: This header is sent if the webhook is configured with a `secret`. This is the HMAC hex digest of the request body, and is generated using the SHA-1 hash function and the `secret` as the HMAC `key`. `X-Hub-Signature` is provided for compatibility with existing integrations. We recommend that you use the more secure `X-Hub-Signature-256` instead. -* `X-Hub-Signature-256`: This header is sent if the webhook is configured with a `secret`. This is the HMAC hex digest of the request body, and is generated using the SHA-256 hash function and the `secret` as the HMAC `key`. For more information, see [AUTOTITLE](/webhooks/using-webhooks/securing-your-webhooks). +* `X-Hub-Signature-256`: This header is sent if the webhook is configured with a `secret`. This is the HMAC hex digest of the request body, and is generated using the SHA-256 hash function and the `secret` as the HMAC `key`. For more information, see [AUTOTITLE](/webhooks/using-webhooks/validating-webhook-deliveries). * `User-Agent`: This header will always have the prefix `GitHub-Hookshot/`. * `X-GitHub-Hook-Installation-Target-Type`: The type of resource where the webhook was created. * `X-GitHub-Hook-Installation-Target-ID`: The unique identifier of the resource where the webhook was created. From ca0be3563766814ea73bbaedf2d3e2e7ad96f883 Mon Sep 17 00:00:00 2001 From: Kevin Heis Date: Thu, 9 Jul 2026 06:42:19 -0700 Subject: [PATCH 13/17] Update redirected internal links in site-policy (#62111) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .../github-acceptable-use-policies.md | 4 ++-- .../github-community-code-of-conduct.md | 4 ++-- .../github-terms/github-community-guidelines.md | 2 +- .../github-corporate-terms-of-service.md | 8 ++++---- .../github-marketplace-terms-of-service.md | 6 +++--- ...pen-source-applications-terms-and-conditions.md | 2 +- .../github-registered-developer-agreement.md | 2 +- .../github-terms/github-research-program-terms.md | 2 +- ...ub-secret-scanning-partner-program-agreement.md | 4 ++-- .../github-sponsors-additional-terms.md | 2 +- ...b-terms-for-additional-products-and-features.md | 14 +++++++------- .../github-terms/github-terms-of-service.md | 2 +- .../github-account-recovery-policy.md | 4 ++-- .../github-deceased-user-policy.md | 4 ++-- .../guidelines-for-legal-requests-of-user-data.md | 4 ++-- .../site-policy/privacy-policies/github-cookies.md | 4 ++-- .../privacy-policies/github-subprocessors.md | 2 +- ...ce-applicable-to-us-federal-government-users.md | 2 +- ...github-enterprise-cloud-evaluation-agreement.md | 2 +- .../github-enterprise-subscription-agreement.md | 8 ++++---- ...emental-terms-for-microsoft-volume-licensing.md | 2 +- 21 files changed, 42 insertions(+), 42 deletions(-) diff --git a/content/site-policy/acceptable-use-policies/github-acceptable-use-policies.md b/content/site-policy/acceptable-use-policies/github-acceptable-use-policies.md index 5100dcce69b9..edf5e776cad9 100644 --- a/content/site-policy/acceptable-use-policies/github-acceptable-use-policies.md +++ b/content/site-policy/acceptable-use-policies/github-acceptable-use-policies.md @@ -92,13 +92,13 @@ Scraping refers to extracting information from our Service via an automated proc You may not use information from the Service (whether scraped, collected through our API, or obtained otherwise) for spamming purposes, including for the purposes of sending unsolicited emails to users or selling personal information, such as to recruiters, headhunters, and job boards. -Your use of information from the Service must comply with the [GitHub Privacy Statement](/site-policy/privacy-policies/github-privacy-statement). +Your use of information from the Service must comply with the [GitHub Privacy Statement](/site-policy/privacy-policies/github-general-privacy-statement). ## 8. Privacy Misuse of personal information is prohibited. -Any person, entity, or service collecting data from the Service must comply with the [GitHub Privacy Statement](/site-policy/privacy-policies/github-privacy-statement), particularly in regards to the collection of personal information. If you collect any personal information from the Service, you agree that you will only use that personal information for the purpose for which that User has authorized it. You agree that you will reasonably secure any personal information you have gathered from the Service, and you will respond promptly to complaints, removal requests, and "do not contact" requests from us or other users. +Any person, entity, or service collecting data from the Service must comply with the [GitHub Privacy Statement](/site-policy/privacy-policies/github-general-privacy-statement), particularly in regards to the collection of personal information. If you collect any personal information from the Service, you agree that you will only use that personal information for the purpose for which that User has authorized it. You agree that you will reasonably secure any personal information you have gathered from the Service, and you will respond promptly to complaints, removal requests, and "do not contact" requests from us or other users. ## 9. Excessive Bandwidth Use diff --git a/content/site-policy/github-terms/github-community-code-of-conduct.md b/content/site-policy/github-terms/github-community-code-of-conduct.md index fc9dc6ea3c0e..4079e490dd5e 100644 --- a/content/site-policy/github-terms/github-community-code-of-conduct.md +++ b/content/site-policy/github-terms/github-community-code-of-conduct.md @@ -122,10 +122,10 @@ Let's work together to keep GitHub Community a place where people feel safe to p ## Legal Notices -Yes, legalese is boring, but we must protect ourselves – and by extension, you and your data – against unfriendly folks. We have a [Terms of Service](/site-policy/github-terms/github-terms-of-service), which includes our [Acceptable Use Policies](/site-policy/acceptable-use-policies/github-acceptable-use-policies), and our [Privacy Statement](/site-policy/privacy-policies/github-privacy-statement) describing your (and our) behavior and rights related to content, privacy, and laws. To use this service, you must agree to abide by our [Terms of Service](/site-policy/github-terms/github-terms-of-service), [GitHub Acceptable Use Policies](/site-policy/acceptable-use-policies/github-acceptable-use-policies) and the [Privacy Statement](/site-policy/privacy-policies/github-privacy-statement). +Yes, legalese is boring, but we must protect ourselves – and by extension, you and your data – against unfriendly folks. We have a [Terms of Service](/site-policy/github-terms/github-terms-of-service), which includes our [Acceptable Use Policies](/site-policy/acceptable-use-policies/github-acceptable-use-policies), and our [Privacy Statement](/site-policy/privacy-policies/github-general-privacy-statement) describing your (and our) behavior and rights related to content, privacy, and laws. To use this service, you must agree to abide by our [Terms of Service](/site-policy/github-terms/github-terms-of-service), [GitHub Acceptable Use Policies](/site-policy/acceptable-use-policies/github-acceptable-use-policies) and the [Privacy Statement](/site-policy/privacy-policies/github-general-privacy-statement). This Code of Conduct does not modify our [Terms of Service](/site-policy/github-terms/github-terms-of-service)—which includes our [Acceptable Use Policies](/site-policy/acceptable-use-policies/github-acceptable-use-policies)—and is not intended to be a complete list. GitHub retains full discretion under the [Terms of Service](/site-policy/github-terms/github-terms-of-service) to remove or restrict any content or accounts for activity that violates those policies, including because it is unlawful, offensive, threatening, libelous, defamatory, pornographic, obscene or otherwise objectionable, or violates any party's intellectual property or our Terms of Service. This Code of Conduct describes when we will exercise that discretion. ### Data Retention and Deletion of Data -If you're a GitHub user, you may access, update, alter, or delete your basic user profile information by [editing your user profile](https://github.com/settings/profile) or contacting GitHub Support through the [GitHub Support portal](https://support.github.com/). We will retain and use your information as necessary to comply with our legal obligations, resolve disputes, and enforce our agreements, but barring legal requirements, will delete your full profile (within reason) within 90 days of your request. For more information please see the [GitHub Privacy Statement](/site-policy/privacy-policies/github-privacy-statement). +If you're a GitHub user, you may access, update, alter, or delete your basic user profile information by [editing your user profile](https://github.com/settings/profile) or contacting GitHub Support through the [GitHub Support portal](https://support.github.com/). We will retain and use your information as necessary to comply with our legal obligations, resolve disputes, and enforce our agreements, but barring legal requirements, will delete your full profile (within reason) within 90 days of your request. For more information please see the [GitHub Privacy Statement](/site-policy/privacy-policies/github-general-privacy-statement). diff --git a/content/site-policy/github-terms/github-community-guidelines.md b/content/site-policy/github-terms/github-community-guidelines.md index 572470bab49e..0eeccbbdb19f 100644 --- a/content/site-policy/github-terms/github-community-guidelines.md +++ b/content/site-policy/github-terms/github-community-guidelines.md @@ -35,7 +35,7 @@ While some disagreements can be resolved with direct, respectful communication b * **Communicate expectations** - Maintainers can set community-specific guidelines to help users understand how to interact with their projects, for example, in a repository’s README, [CONTRIBUTING file](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors), or [dedicated code of conduct](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project). You can find additional information on building communities on the [Communities](/communities) page. -* **Moderate Comments** - Users with [write-access privileges](/organizations/managing-user-access-to-your-organizations-repositories/repository-roles-for-an-organization) for a repository can [edit, delete, or hide anyone's comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments) on commits, pull requests, and issues. Anyone with read access to a repository can view a comment's edit history. Comment authors and people with write access to a repository can also delete sensitive information from a [comment's edit history](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment). Moderating your projects can feel like a big task if there is a lot of activity, but you can [add collaborators](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository#collaborator-access-for-a-repository-owned-by-a-personal-account) to assist you in managing your community. +* **Moderate Comments** - Users with [write-access privileges](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization) for a repository can [edit, delete, or hide anyone's comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments) on commits, pull requests, and issues. Anyone with read access to a repository can view a comment's edit history. Comment authors and people with write access to a repository can also delete sensitive information from a [comment's edit history](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment). Moderating your projects can feel like a big task if there is a lot of activity, but you can [add collaborators](/repositories/managing-your-repositorys-settings-and-features/repository-access-and-collaboration/permission-levels-for-a-personal-account-repository#collaborator-access-for-a-repository-owned-by-a-personal-account) to assist you in managing your community. * **Lock Conversations**  - If a discussion in an issue, pull request, or commit gets out of hand, off topic, or violates your project’s code of conduct or GitHub’s policies, owners, collaborators, and anyone else with write access can put a temporary or permanent lock on the conversation. For more information, see [AUTOTITLE](/communities/moderating-comments-and-conversations/locking-conversations). diff --git a/content/site-policy/github-terms/github-corporate-terms-of-service.md b/content/site-policy/github-terms/github-corporate-terms-of-service.md index 3fd1d512861c..411ed28fc54d 100644 --- a/content/site-policy/github-terms/github-corporate-terms-of-service.md +++ b/content/site-policy/github-terms/github-corporate-terms-of-service.md @@ -135,7 +135,7 @@ Customer’s use of the Service must comply with [GitHub's Acceptable Use Polici ### 3. Privacy -The [GitHub Privacy Statement](/site-policy/privacy-policies/github-privacy-statement) and the [GitHub Data Protection Agreement](https://github.com/customer-terms) provide detailed notice of GitHub's privacy and data use practices as well as GitHub's processing and security obligations with respect to Customer Personal Data. Any person, entity, or service collecting data from the Service must comply with the GitHub Privacy Statement, particularly in regards to the collection of personal data (as defined in the GitHub Privacy Statement). If Customer collects any personal information from GitHub, Customer will only use it for the purpose for which the External User has authorized it. Customer will reasonably secure any such Personal Information, and Customer will respond promptly to complaints, removal requests, and "do not contact" requests from GitHub or External Users. +The [GitHub Privacy Statement](/site-policy/privacy-policies/github-general-privacy-statement) and the [GitHub Data Protection Agreement](https://github.com/customer-terms) provide detailed notice of GitHub's privacy and data use practices as well as GitHub's processing and security obligations with respect to Customer Personal Data. Any person, entity, or service collecting data from the Service must comply with the GitHub Privacy Statement, particularly in regards to the collection of personal data (as defined in the GitHub Privacy Statement). If Customer collects any personal information from GitHub, Customer will only use it for the purpose for which the External User has authorized it. Customer will reasonably secure any such Personal Information, and Customer will respond promptly to complaints, removal requests, and "do not contact" requests from GitHub or External Users. ## D. Content Responsibility; Ownership; License Rights @@ -177,13 +177,13 @@ GitHub considers Customer Content in Customer’s Private Repositories to be Cus ### 3. Access -GitHub personnel may only access Customer's Private Repositories in the situations described in our [Privacy Statement](/site-policy/privacy-policies/github-privacy-statement#repository-contents). +GitHub personnel may only access Customer's Private Repositories in the situations described in our [Privacy Statement](/site-policy/privacy-policies/github-general-privacy-statement#private-repositories-github-access). Customer may choose to enable additional access to its Private Repositories. For example, Customer may enable various GitHub services or features that require additional rights to Customer Content in Private Repositories. These rights may vary depending on the service or feature, but GitHub will continue to treat Customer Content in Customer’s Private Repositories as Customer’s Confidential Information. If those services or features require rights in addition to those it needs to provide the Service, GitHub will provide an explanation of those rights. -Additionally, we may be [compelled by law](/site-policy/privacy-policies/github-privacy-statement#for-legal-disclosure) to disclose the contents of your private repositories. +Additionally, we may be [compelled by law](/site-policy/privacy-policies/github-general-privacy-statement#sharing-of-personal-data) to disclose the contents of your private repositories. -GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/site-policy/privacy-policies/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. +GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/site-policy/privacy-policies/github-general-privacy-statement#sharing-of-personal-data), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. ## F. Intellectual Property Notice diff --git a/content/site-policy/github-terms/github-marketplace-terms-of-service.md b/content/site-policy/github-terms/github-marketplace-terms-of-service.md index 6e9e6edb0ea2..c437f1b14124 100644 --- a/content/site-policy/github-terms/github-marketplace-terms-of-service.md +++ b/content/site-policy/github-terms/github-marketplace-terms-of-service.md @@ -43,7 +43,7 @@ If you would have a question, concern, or dispute regarding your billing, please ## E. Your Data and GitHub's Privacy Policy -**Privacy.** When you select or use a Developer Product, GitHub may share certain Personal Information (as defined in the [GitHub Privacy Statement](/site-policy/privacy-policies/github-privacy-statement)) with the Product Provider (if any such Personal Information is received from you) in order to provide you with the Developer Product, regardless of your privacy settings. Depending on the requirements of the Developer Product you choose, GitHub may share as little as your account name, ID, and primary email address or as much as access to the content in your repositories, including the ability to read and modify your private data. You will be able to view the scope of the permissions the Developer Product is requesting, and accept or deny them, when you grant it authorization via OAuth. +**Privacy.** When you select or use a Developer Product, GitHub may share certain Personal Information (as defined in the [GitHub Privacy Statement](/site-policy/privacy-policies/github-general-privacy-statement)) with the Product Provider (if any such Personal Information is received from you) in order to provide you with the Developer Product, regardless of your privacy settings. Depending on the requirements of the Developer Product you choose, GitHub may share as little as your account name, ID, and primary email address or as much as access to the content in your repositories, including the ability to read and modify your private data. You will be able to view the scope of the permissions the Developer Product is requesting, and accept or deny them, when you grant it authorization via OAuth. If you cease using the Developer Product and revoke access through your account settings, the Product Provider will no longer be able to access your account. The Product Provider is responsible for deleting your Personal Information from its systems within its defined window. Please contact the Product Provider to ensure that your account has been properly terminated. @@ -77,11 +77,11 @@ You agree to indemnify us, defend us, and hold us harmless from and against any 1. **Governing Law.** You agree that these Marketplace Terms and your use of the Developer Products are governed under California law and any dispute related to the Developer Products must be brought in a tribunal of competent jurisdiction located in or near San Francisco, California. -1. **Non-Assignability.** GitHub may assign or delegate these Marketplace Terms and/or the [GitHub's Privacy Statement](/site-policy/privacy-policies/github-privacy-statement), in whole or in part, to any person or entity at any time with or without your consent. You may not assign or delegate any rights or obligations under the Marketplace Terms or Privacy Statement without our prior written consent, and any unauthorized assignment and delegation by you is void. +1. **Non-Assignability.** GitHub may assign or delegate these Marketplace Terms and/or the [GitHub's Privacy Statement](/site-policy/privacy-policies/github-general-privacy-statement), in whole or in part, to any person or entity at any time with or without your consent. You may not assign or delegate any rights or obligations under the Marketplace Terms or Privacy Statement without our prior written consent, and any unauthorized assignment and delegation by you is void. 1. **Severability, No Waiver, and Survival.** If any part of these Marketplace Terms are held invalid or unenforceable, that portion of the Marketplace Terms will be construed to reflect the parties’ original intent. The remaining portions will remain in full force and effect. The failure of GitHub to exercise or enforce any right or provision of these Marketplace Terms shall not constitute a waiver of such right or provision. Our rights under these Marketplace Terms will survive any termination of these Marketplace Terms. -1. **No Modifications; Complete Agreement.** These Marketplace Terms may only be modified by a written amendment signed by an authorized representative of GitHub, or by the posting by GitHub of a revised version. These Marketplace Terms, together with [GitHub's Privacy Statement](/site-policy/privacy-policies/github-privacy-statement), represent the complete and exclusive statement of the agreement between you and us. These Marketplace Terms supersede any proposal or prior agreement oral or written, and any other communications between you and GitHub relating to the subject matter of these terms. +1. **No Modifications; Complete Agreement.** These Marketplace Terms may only be modified by a written amendment signed by an authorized representative of GitHub, or by the posting by GitHub of a revised version. These Marketplace Terms, together with [GitHub's Privacy Statement](/site-policy/privacy-policies/github-general-privacy-statement), represent the complete and exclusive statement of the agreement between you and us. These Marketplace Terms supersede any proposal or prior agreement oral or written, and any other communications between you and GitHub relating to the subject matter of these terms. 1. **Section Headings.** Throughout these Marketplace Terms, each section includes titles of the following terms and conditions. These section titles are not legally binding. diff --git a/content/site-policy/github-terms/github-open-source-applications-terms-and-conditions.md b/content/site-policy/github-terms/github-open-source-applications-terms-and-conditions.md index ab2bbc0c787f..3b4d7988c672 100644 --- a/content/site-policy/github-terms/github-open-source-applications-terms-and-conditions.md +++ b/content/site-policy/github-terms/github-open-source-applications-terms-and-conditions.md @@ -33,7 +33,7 @@ The names GitHub, GitHub Desktop, GitHub for Mac, GitHub for Windows, the Octoca ## Privacy -The Software may collect personal information. You may control what information the Software collects in the settings panel. If the Software does collect personal information on GitHub's behalf, GitHub will process that information in accordance with the [GitHub Privacy Statement](/site-policy/privacy-policies/github-privacy-statement). +The Software may collect personal information. You may control what information the Software collects in the settings panel. If the Software does collect personal information on GitHub's behalf, GitHub will process that information in accordance with the [GitHub Privacy Statement](/site-policy/privacy-policies/github-general-privacy-statement). ## Additional Services diff --git a/content/site-policy/github-terms/github-registered-developer-agreement.md b/content/site-policy/github-terms/github-registered-developer-agreement.md index 05df7975b751..b42242a132b7 100644 --- a/content/site-policy/github-terms/github-registered-developer-agreement.md +++ b/content/site-policy/github-terms/github-registered-developer-agreement.md @@ -18,7 +18,7 @@ This Agreement is a legal agreement between you (“you”) and GitHub, Inc. ( 1. **Program Terms** - We post the [Program’s benefits and guidelines](/get-started/exploring-integrations/github-developer-program) (the “Program Overview”). As you might expect, the Program Overview will change from time to time. These changes will apply to you as a participant in the Program, so we encourage you to periodically review the Program Overview to keep apprised of any changes. For a variety of reasons, we might need to change, suspend, or discontinue the Program, or some of the benefits we offer. You agree that we can do those things without liability to you, except as specified in Section 9. + We post the [Program’s benefits and guidelines](/integrations/concepts/github-developer-program) (the “Program Overview”). As you might expect, the Program Overview will change from time to time. These changes will apply to you as a participant in the Program, so we encourage you to periodically review the Program Overview to keep apprised of any changes. For a variety of reasons, we might need to change, suspend, or discontinue the Program, or some of the benefits we offer. You agree that we can do those things without liability to you, except as specified in Section 9. 1. **API License** diff --git a/content/site-policy/github-terms/github-research-program-terms.md b/content/site-policy/github-terms/github-research-program-terms.md index 4bca5e457951..88ccb1ddf71d 100644 --- a/content/site-policy/github-terms/github-research-program-terms.md +++ b/content/site-policy/github-terms/github-research-program-terms.md @@ -35,7 +35,7 @@ All Confidential Information remains the sole and exclusive property of GitHub. By participating in this Program, you consent to our use of your personal information for research purposes, and not for any other purposes. As part of the Program, we may use your personal information to contact you, or retain your information, to contact you at a later date. Personal information does not include aggregated, non-personally identifying information. We may use aggregated or other non-personally identifying information collected through the program to operate, analyze, and improve our products and services. -You can withdraw your consent at any time, and request access to or the deletion of the personal information that we hold about you. For more information about how you can access, update, alter, or delete the personal information GitHub collects through the Program, please see the [GitHub Privacy Statement](/site-policy/privacy-policies/github-privacy-statement) or contact us through our {% data variables.contact.contact_privacy %}. +You can withdraw your consent at any time, and request access to or the deletion of the personal information that we hold about you. For more information about how you can access, update, alter, or delete the personal information GitHub collects through the Program, please see the [GitHub Privacy Statement](/site-policy/privacy-policies/github-general-privacy-statement) or contact us through our {% data variables.contact.contact_privacy %}. ## E. GitHub Services and Software Terms diff --git a/content/site-policy/github-terms/github-secret-scanning-partner-program-agreement.md b/content/site-policy/github-terms/github-secret-scanning-partner-program-agreement.md index 7e24e6a3c909..f62bf0c642f3 100644 --- a/content/site-policy/github-terms/github-secret-scanning-partner-program-agreement.md +++ b/content/site-policy/github-terms/github-secret-scanning-partner-program-agreement.md @@ -35,7 +35,7 @@ category: **"Program"** means the GitHub Secret Scanning Partner Program. -**"Program Documentation"** means GitHub's published documentation for the Program, currently available at [https://docs.github.com/code-security/secret-scanning/secret-scanning-partner-program](/code-security/secret-scanning/secret-scanning-partner-program), as GitHub may update it. +**"Program Documentation"** means GitHub's published documentation for the Program, currently available at [https://docs.github.com/code-security/secret-scanning/secret-scanning-partner-program](/code-security/tutorials/secret-scanning-partner-program), as GitHub may update it. **"Token Patterns"** means the technical specifications that Partner provides to GitHub for use in the Program, including: (a) a unique, human-readable name for each credential type; (b) regular expressions and multi-part relationship rules that identify the credential type; (c) post-processing logic, exclusion patterns, validation endpoints, and format documentation; and (d) any other technical information that Partner provides to GitHub in connection with the Program's pattern-matching functionality. @@ -237,7 +237,7 @@ The Program Documentation is part of this agreement. If there is a conflict betw ### 12.2 Amendments to this Agreement -GitHub may amend this agreement (including the Program Documentation) at any time by posting a revised version to [https://docs.github.com/code-security/secret-scanning/secret-scanning-partner-program](/code-security/secret-scanning/secret-scanning-partner-program) and providing Partner at least 30 days' advance notice via email to the address Partner provided during onboarding. Partner's continued participation in the Program following the 30-day notice period constitutes Partner's acceptance of that amendment. Partner may terminate this agreement under Section 16.2 before the amendment takes effect. +GitHub may amend this agreement (including the Program Documentation) at any time by posting a revised version to [https://docs.github.com/code-security/secret-scanning/secret-scanning-partner-program](/code-security/tutorials/secret-scanning-partner-program) and providing Partner at least 30 days' advance notice via email to the address Partner provided during onboarding. Partner's continued participation in the Program following the 30-day notice period constitutes Partner's acceptance of that amendment. Partner may terminate this agreement under Section 16.2 before the amendment takes effect. ### 12.3 Program Changes diff --git a/content/site-policy/github-terms/github-sponsors-additional-terms.md b/content/site-policy/github-terms/github-sponsors-additional-terms.md index 42450482889b..d94fa0626c50 100644 --- a/content/site-policy/github-terms/github-sponsors-additional-terms.md +++ b/content/site-policy/github-terms/github-sponsors-additional-terms.md @@ -135,7 +135,7 @@ You will: (A) create a Sponsored Developer Account; (B) make Sponsored Developer ### 2.2. Registration. -If you choose to apply for the Program, entry into the Program is contingent upon your completion of the registration process and acceptance into the Program by GitHub. In addition, you may be required to register with the payment service provider(s) selected by GitHub (such as Stripe) in order to access and use certain features of the Program. You must register with your true identity, and you agree to provide and maintain true, accurate, current and complete information about yourself as requested by the Program's registration form. Registration data and certain other information about you are governed by our [Privacy Statement](/site-policy/privacy-policies/github-privacy-statement), as well as any privacy statement provided by our payment processor. GitHub reserves the right to refuse acceptance into the Program. +If you choose to apply for the Program, entry into the Program is contingent upon your completion of the registration process and acceptance into the Program by GitHub. In addition, you may be required to register with the payment service provider(s) selected by GitHub (such as Stripe) in order to access and use certain features of the Program. You must register with your true identity, and you agree to provide and maintain true, accurate, current and complete information about yourself as requested by the Program's registration form. Registration data and certain other information about you are governed by our [Privacy Statement](/site-policy/privacy-policies/github-general-privacy-statement), as well as any privacy statement provided by our payment processor. GitHub reserves the right to refuse acceptance into the Program. ### 2.3. Content Monetization. diff --git a/content/site-policy/github-terms/github-terms-for-additional-products-and-features.md b/content/site-policy/github-terms/github-terms-for-additional-products-and-features.md index 69055bb2626d..4494a579f511 100644 --- a/content/site-policy/github-terms/github-terms-for-additional-products-and-features.md +++ b/content/site-policy/github-terms/github-terms-for-additional-products-and-features.md @@ -28,7 +28,7 @@ By using the Additional Products and Features, you also agree to the applicable GitHub Actions enables you to create custom software development lifecycle workflows directly in your GitHub repository. Actions is billed on a usage basis. The [Actions documentation](/actions) includes details, including compute and storage quantities (depending on your Account plan), and how to monitor your Actions minutes usage and set usage limits. -Actions and any elements of the Actions product or service may not be used in violation of the Agreement, the [GitHub Acceptable Use Policies](/site-policy/acceptable-use-policies/github-acceptable-use-policies), or the GitHub Actions service limitations set forth in the [Actions documentation](/actions/learn-github-actions/usage-limits-billing-and-administration). Additionally, regardless of whether an Action is using self-hosted runners, Actions should not be used for: +Actions and any elements of the Actions product or service may not be used in violation of the Agreement, the [GitHub Acceptable Use Policies](/site-policy/acceptable-use-policies/github-acceptable-use-policies), or the GitHub Actions service limitations set forth in the [Actions documentation](/actions/concepts/billing-and-usage). Additionally, regardless of whether an Action is using self-hosted runners, Actions should not be used for: * Cryptomining; * Disrupting, gaining, or attempting to gain unauthorized access to, any service, device, data, account, or network (other than those authorized by the [GitHub Bug Bounty program](https://bounty.github.com)); * The provision of a stand-alone or integrated application or service offering the Actions product or service, or any elements of the Actions product or service, for commercial purposes; @@ -59,7 +59,7 @@ GitHub makes extra security features available to customers under Advanced Secur Advanced Security features are licensed on a "Unique Committer" basis. A "Unique Committer" is a licensed user of GitHub Team, GitHub Enterprise, GitHub Enterprise Cloud, or GitHub Enterprise Server, who has made a commit in the last 90 days to any repository with any GitHub Advanced Security functionality activated. You must acquire an appropriate GitHub Advanced Security User license for each of your Unique Committers. You may only use GitHub Advanced Security features on codebases that are developed by or for you. For GitHub Team and GitHub Enterprise Cloud users, some Advanced Security features may also require the use of GitHub Actions. -For secret scanning with GitHub Advanced Security or GitHub Secret Protection, when you opt-in to automatic validity checks for partner patterns, exposed third-party tokens may be shared with the relevant partner, in order to provide you with more information about the validity of the token. Not all partners are based in the United States. The [Secret scanning patterns documentation](/enterprise-cloud@latest/code-security/secret-scanning/introduction/supported-secret-scanning-patterns) provides more details on which partners support the validity check. +For secret scanning with GitHub Advanced Security or GitHub Secret Protection, when you opt-in to automatic validity checks for partner patterns, exposed third-party tokens may be shared with the relevant partner, in order to provide you with more information about the validity of the token. Not all partners are based in the United States. The [Secret scanning patterns documentation](/enterprise-cloud@latest/code-security/reference/secret-security/supported-secret-scanning-patterns) provides more details on which partners support the validity check. ## Advisory Database @@ -96,7 +96,7 @@ If you offer a product or service competitive to any GitHub product or service, ## Connect -With GitHub Connect, you can share certain features and data between your GitHub Enterprise Server deployment and your GitHub Enterprise Cloud organization or enterprise account on GitHub.com. In order to enable GitHub Connect, you must have at least one (1) account on GitHub Enterprise Cloud or GitHub.com, and one (1) licensed deployment of GitHub Enterprise Server. Your use of GitHub Enterprise Cloud or GitHub.com through Connect is governed by the terms under which you license GitHub Enterprise Cloud or GitHub.com. Use of Personal Data is governed by the [GitHub Privacy Statement](/site-policy/privacy-policies/github-privacy-statement). +With GitHub Connect, you can share certain features and data between your GitHub Enterprise Server deployment and your GitHub Enterprise Cloud organization or enterprise account on GitHub.com. In order to enable GitHub Connect, you must have at least one (1) account on GitHub Enterprise Cloud or GitHub.com, and one (1) licensed deployment of GitHub Enterprise Server. Your use of GitHub Enterprise Cloud or GitHub.com through Connect is governed by the terms under which you license GitHub Enterprise Cloud or GitHub.com. Use of Personal Data is governed by the [GitHub Privacy Statement](/site-policy/privacy-policies/github-general-privacy-statement). ## GitHub Copilot @@ -118,17 +118,17 @@ GitHub Packages is a software package hosting service that allows you to host yo ## Pages -Each Account comes with access to the [GitHub Pages static hosting service](/pages/getting-started-with-github-pages/about-github-pages). GitHub Pages is intended to host static web pages, but primarily as a showcase for personal and organizational projects. +Each Account comes with access to the [GitHub Pages static hosting service](/pages/getting-started-with-github-pages/what-is-github-pages). GitHub Pages is intended to host static web pages, but primarily as a showcase for personal and organizational projects. GitHub Pages is not intended for or allowed to be used as a free web hosting service to run your online business, e-commerce site, or any other website that is primarily directed at either facilitating commercial transactions or providing commercial software as a service (SaaS). Some monetization efforts are permitted on Pages, such as donation buttons and crowdfunding links. _Bandwidth and Usage Limits_ -GitHub Pages are subject to some specific bandwidth and usage limits, and may not be appropriate for some high-bandwidth uses. Please see our [GitHub Pages limits](/pages/getting-started-with-github-pages/about-github-pages) for more information. +GitHub Pages are subject to some specific bandwidth and usage limits, and may not be appropriate for some high-bandwidth uses. Please see our [GitHub Pages limits](/pages/getting-started-with-github-pages/github-pages-limits) for more information. _Prohibited Uses_ -GitHub Pages may not be used in violation of the Agreement, the GitHub [Acceptable Use Policies](/site-policy/acceptable-use-policies/github-acceptable-use-policies), or the GitHub Pages service limitations set forth in the [Pages documentation](/pages/getting-started-with-github-pages/about-github-pages#guidelines-for-using-github-pages). +GitHub Pages may not be used in violation of the Agreement, the GitHub [Acceptable Use Policies](/site-policy/acceptable-use-policies/github-acceptable-use-policies), or the GitHub Pages service limitations set forth in the [Pages documentation](/pages/getting-started-with-github-pages/github-pages-limits#usage-limits). If you have questions about whether your use or intended use falls into these categories, please contact us through the [GitHub Support portal](https://support.github.com/). GitHub reserves the right at all times to reclaim any GitHub subdomain without liability. @@ -150,6 +150,6 @@ You may download Microsoft SQL Server Standard Edition container image for Linux ## GitHub Models -GitHub Models is a feature that allows you to learn, try, and test artificial intelligence models on GitHub.com. You can access GitHub Models via the [GitHub Marketplace](https://github.com/marketplace). Learn more about GitHub Models by visiting [Prototyping with AI models](/github-models/prototyping-with-ai-models). +GitHub Models is a feature that allows you to learn, try, and test artificial intelligence models on GitHub.com. You can access GitHub Models via the [GitHub Marketplace](https://github.com/marketplace). Learn more about GitHub Models by visiting [Prototyping with AI models](/github-models/use-github-models/prototyping-with-ai-models). Your use of this feature is subject to the terms of the company hosting the model and the model license. diff --git a/content/site-policy/github-terms/github-terms-of-service.md b/content/site-policy/github-terms/github-terms-of-service.md index 1312224e6c03..9616aba52de0 100644 --- a/content/site-policy/github-terms/github-terms-of-service.md +++ b/content/site-policy/github-terms/github-terms-of-service.md @@ -326,7 +326,7 @@ You are responsible for all fees, including taxes, associated with your use of t ### 1. Account Cancellation -It is your responsibility to properly cancel your Account with GitHub. You can [cancel your Account at any time](/billing/managing-the-plan-for-your-github-account/downgrading-your-accounts-plan) by going into your Settings in the global navigation bar at the top of the screen. The Account screen provides a simple, no questions asked cancellation link. We are not able to cancel Accounts in response to an email or phone request. +It is your responsibility to properly cancel your Account with GitHub. You can [cancel your Account at any time](/billing/how-tos/manage-plan-and-licenses/downgrade-plan) by going into your Settings in the global navigation bar at the top of the screen. The Account screen provides a simple, no questions asked cancellation link. We are not able to cancel Accounts in response to an email or phone request. ### 2. Upon Cancellation diff --git a/content/site-policy/other-site-policies/github-account-recovery-policy.md b/content/site-policy/other-site-policies/github-account-recovery-policy.md index 098e350fb6e0..b225cb7d783b 100644 --- a/content/site-policy/other-site-policies/github-account-recovery-policy.md +++ b/content/site-policy/other-site-policies/github-account-recovery-policy.md @@ -8,7 +8,7 @@ category: GitHub provides [a number of account recovery methods](/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials) including an [automated recovery process](/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials#authenticating-with-a-verified-device-ssh-token-or-personal-access-token) if you have lost access to your GitHub.com account. **If you cannot use any of the provided recovery methods, you have permanently lost access to your account.** -You can, however, [unlink email addresses](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/unlinking-your-email-address-from-a-locked-account) from a locked account in order to create a new account or use the email on another existing account. +You can, however, [unlink email addresses](/account-and-profile/how-tos/account-management/unlinking-your-email-address-from-a-locked-account) from a locked account in order to create a new account or use the email on another existing account. ## Can I open a support ticket to recover my account? @@ -18,7 +18,7 @@ GitHub does not support any other means of account recovery, including social or ## How can I retrieve my email from a locked account? -See [Unlinking your email address from a locked account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/unlinking-your-email-address-from-a-locked-account). +See [Unlinking your email address from a locked account](/account-and-profile/how-tos/account-management/unlinking-your-email-address-from-a-locked-account). ## How can I remove a payment method from a locked account? diff --git a/content/site-policy/other-site-policies/github-deceased-user-policy.md b/content/site-policy/other-site-policies/github-deceased-user-policy.md index 65b29bd2320f..3dbcb19851bb 100644 --- a/content/site-policy/other-site-policies/github-deceased-user-policy.md +++ b/content/site-policy/other-site-policies/github-deceased-user-policy.md @@ -11,7 +11,7 @@ category: In the event that a GitHub user passes away, we can work with an authorized individual to determine what happens to the account's content. -If you are next of kin, a [pre-designated successor](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories), or other authorized individual (which could include a collaborator or business partner) of a deceased user and would like to make a request regarding their account, you can reach out to us through the [GitHub Support portal](https://support.github.com/). In the portal, click **Contact us**, and provide the following information in your message: +If you are next of kin, a [pre-designated successor](/repositories/managing-your-repositorys-settings-and-features/repository-access-and-collaboration/maintaining-ownership-continuity-of-your-personal-accounts-repositories), or other authorized individual (which could include a collaborator or business partner) of a deceased user and would like to make a request regarding their account, you can reach out to us through the [GitHub Support portal](https://support.github.com/). In the portal, click **Contact us**, and provide the following information in your message: * Name * Contact Information @@ -23,4 +23,4 @@ If you are next of kin, a [pre-designated successor](/account-and-profile/settin Once we have received your request, we may follow up with a request for additional information, such as a copy of your photo identification, copy of the death certificate, and documentation confirming you are authorized to act in relation to the deceased user’s account, to verify that we are properly authorized to process your request. -Please note, the information you provide in your request is collected in accordance with our [Privacy Statement](/site-policy/privacy-policies/github-privacy-statement), and we will retain the information only as necessary to comply with our legal obligations and resolve disputes. +Please note, the information you provide in your request is collected in accordance with our [Privacy Statement](/site-policy/privacy-policies/github-general-privacy-statement), and we will retain the information only as necessary to comply with our legal obligations and resolve disputes. diff --git a/content/site-policy/other-site-policies/guidelines-for-legal-requests-of-user-data.md b/content/site-policy/other-site-policies/guidelines-for-legal-requests-of-user-data.md index 77064f03a3e1..9ede56a888d4 100644 --- a/content/site-policy/other-site-policies/guidelines-for-legal-requests-of-user-data.md +++ b/content/site-policy/other-site-policies/guidelines-for-legal-requests-of-user-data.md @@ -60,7 +60,7 @@ They may be easiest to imagine as a project's folder. A repository contains all of the project files (including documentation), and stores each file's revision history. Repositories can have multiple collaborators and, at its administrators' discretion, may be publicly viewable or not. -* [**Pages**](/pages/getting-started-with-github-pages/about-github-pages): +* [**Pages**](/pages/getting-started-with-github-pages/what-is-github-pages): GitHub Pages are public webpages freely hosted by GitHub that users can easily publish through code stored in their repositories. If a user or organization has a GitHub Page, it can usually be found at a URL such as `https://username.github.io` or they may have the webpage mapped to their own custom domain name. @@ -96,7 +96,7 @@ All user public profiles display: * **Private account data:** -GitHub also collects and maintains certain private information about users as outlined in our [Privacy Policy](/site-policy/privacy-policies/github-privacy-statement). +GitHub also collects and maintains certain private information about users as outlined in our [Privacy Policy](/site-policy/privacy-policies/github-general-privacy-statement). This may include: * Private email addresses * Payment details diff --git a/content/site-policy/privacy-policies/github-cookies.md b/content/site-policy/privacy-policies/github-cookies.md index 20c200ff0b7d..7c16d7634838 100644 --- a/content/site-policy/privacy-policies/github-cookies.md +++ b/content/site-policy/privacy-policies/github-cookies.md @@ -14,9 +14,9 @@ category: GitHub provides a great deal of transparency regarding how we use your data, how we collect your data, and with whom we share your data. To that end, we provide this page which details how we use cookies. -GitHub uses cookies to provide and secure our websites, as well as to analyze the usage of our websites, in order to offer you a great user experience. Please take a look at our [Privacy Statement](/github/site-policy/github-privacy-statement#our-use-of-cookies-and-tracking-technologies) if you’d like more information about cookies, and on how and why we use them and cookie-related personal data. You can change your preference about non-essential cookies at any time by following [these instructions](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-cookie-preferences-for-githubs-enterprise-marketing-pages). +GitHub uses cookies to provide and secure our websites, as well as to analyze the usage of our websites, in order to offer you a great user experience. Please take a look at our [Privacy Statement](/site-policy/privacy-policies/github-general-privacy-statement#our-use-of-cookies-and-tracking-technologies) if you’d like more information about cookies, and on how and why we use them and cookie-related personal data. You can change your preference about non-essential cookies at any time by following [these instructions](/account-and-profile/how-tos/account-settings/manage-cookie-preferences). -Since the number and names of cookies may change, the table below may be updated from time to time. To receive notifications of updates to this list, please follow the instructions provided in [About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications). +Since the number and names of cookies may change, the table below may be updated from time to time. To receive notifications of updates to this list, please follow the instructions provided in [About notifications](/subscriptions-and-notifications/concepts/about-notifications). Provider of Cookie | Cookie Name | Description | Expiration* -----------------|-------------|-------------|------------ diff --git a/content/site-policy/privacy-policies/github-subprocessors.md b/content/site-policy/privacy-policies/github-subprocessors.md index c841560cbe8f..51bfce268803 100644 --- a/content/site-policy/privacy-policies/github-subprocessors.md +++ b/content/site-policy/privacy-policies/github-subprocessors.md @@ -18,7 +18,7 @@ The GitHub Subprocessor List identifies subprocessors authorized to subprocess c GitHub publishes the names of any new subprocessors for its online services at least 30 days in advance of the subprocessor’s authorization to perform services that may involve access to customer data or personal data. -To receive notifications of updates to this Subprocessor list, please follow the instructions provided in [AUTOTITLE](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications). +To receive notifications of updates to this Subprocessor list, please follow the instructions provided in [AUTOTITLE](/subscriptions-and-notifications/concepts/about-notifications). If you have questions about this list, please contact us at . diff --git a/content/site-policy/site-policy-deprecated/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users.md b/content/site-policy/site-policy-deprecated/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users.md index 2dce0a965f56..efa28fc85247 100644 --- a/content/site-policy/site-policy-deprecated/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users.md +++ b/content/site-policy/site-policy-deprecated/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users.md @@ -36,7 +36,7 @@ GitHub and You (together, the "Parties") agree that modifications to the [GitHub 1. _No endorsement_ - Company agrees that Your seals, trademarks, logos, service marks, trade names, and the fact that You have a presence on the Company site and use its services, shall not be used by Company in such a manner as to state or imply that Company's products or services are endorsed, sponsored or recommended by You or by any other element of the federal government, or are considered by these entities to be superior to any other products or services. Except for pages whose design and content is under the control of the Government, or for links to or promotion of such pages, Company agrees not to display any government seals or logos on the Company's homepage or elsewhere on the Company Site, unless permission to do so has been granted by the Government or by other relevant federal government authority. Company may list the Government's name in a publicly available customer list so long as the name is not displayed in a more prominent fashion than that of any other third-party name. -1. _Provision of data_ - In case of termination of service, within 30 days of such termination, upon request, Company will provide you with all user-generated content that is publicly visible through the Sites You created at Company. Data will be provided in a commonly used file or database format as Company deems appropriate. Company will not provide data if doing so would violate its privacy policy, available at [https://docs.github.com/privacy](/site-policy/privacy-policies/github-privacy-statement). +1. _Provision of data_ - In case of termination of service, within 30 days of such termination, upon request, Company will provide you with all user-generated content that is publicly visible through the Sites You created at Company. Data will be provided in a commonly used file or database format as Company deems appropriate. Company will not provide data if doing so would violate its privacy policy, available at [https://docs.github.com/privacy](/site-policy/privacy-policies/github-general-privacy-statement). ## C. Unpaid and paid plans diff --git a/content/site-policy/site-policy-deprecated/github-enterprise-cloud-evaluation-agreement.md b/content/site-policy/site-policy-deprecated/github-enterprise-cloud-evaluation-agreement.md index 2ceb6dc17b61..67eade158379 100644 --- a/content/site-policy/site-policy-deprecated/github-enterprise-cloud-evaluation-agreement.md +++ b/content/site-policy/site-policy-deprecated/github-enterprise-cloud-evaluation-agreement.md @@ -38,7 +38,7 @@ IN NO EVENT WILL GITHUB BE LIABLE TO CUSTOMER OR TO ANY THIRD PARTY FOR ANY INDI 5.1 As part of the development and evaluation of our evaluation programs, GitHub needs to collect information about how Customer uses services and programs and how GitHub can improve them. GitHub may collect certain additional personal information from Customer. For example, GitHub may invite Customer to provide Feedback (as explained in Section 6 below). GitHub might ask questions about Customer's experiences, familiarity with the product, or demographic information. GitHub uses this information to improve its products and services and does not sell Feedback to third parties or advertisers. Customer may decline to provide Feedback, decline to answer specific questions, or contact GitHub to delete or alter the information it has collected about Customer. -5.2 GitHub's servers are located in the United States. GitHub processes Customer's data in the United States. However, Customer is responsible for determining what personal data it submits to GitHub. Please see the [Privacy Statement](/site-policy/privacy-policies/github-privacy-statement) for more information. +5.2 GitHub's servers are located in the United States. GitHub processes Customer's data in the United States. However, Customer is responsible for determining what personal data it submits to GitHub. Please see the [Privacy Statement](/site-policy/privacy-policies/github-general-privacy-statement) for more information. ## 6. Feedback diff --git a/content/site-policy/site-policy-deprecated/github-enterprise-subscription-agreement.md b/content/site-policy/site-policy-deprecated/github-enterprise-subscription-agreement.md index e33c43318677..9830a95a47ff 100644 --- a/content/site-policy/site-policy-deprecated/github-enterprise-subscription-agreement.md +++ b/content/site-policy/site-policy-deprecated/github-enterprise-subscription-agreement.md @@ -284,7 +284,7 @@ Customer’s use of the Service must comply with [GitHub's Acceptable Use Polici #### 3.2.3 Privacy. -[The GitHub Privacy Statement](/site-policy/privacy-policies/github-privacy-statement) and the [GitHub Data Protection Addendum](https://github.com/customer-terms) provide detailed notice of GitHub's privacy and data use practices as well as GitHub's processing and security obligations with respect to Customer Personal Data. Any person, entity, or service collecting data from the Service must comply with the [GitHub Privacy Statement](/site-policy/privacy-policies/github-privacy-statement), particularly in regards to the collection of Users' Personal Information (as defined in the GitHub Privacy Statement). If Customer collects any User Personal Information from GitHub, Customer will only use it for the purpose for which the External User has authorized it. Customer will reasonably secure any such Personal Information, and Customer will respond promptly to complaints, removal requests, and "do not contact" requests from GitHub or External Users. +[The GitHub Privacy Statement](/site-policy/privacy-policies/github-general-privacy-statement) and the [GitHub Data Protection Addendum](https://github.com/customer-terms) provide detailed notice of GitHub's privacy and data use practices as well as GitHub's processing and security obligations with respect to Customer Personal Data. Any person, entity, or service collecting data from the Service must comply with the [GitHub Privacy Statement](/site-policy/privacy-policies/github-general-privacy-statement), particularly in regards to the collection of Users' Personal Information (as defined in the GitHub Privacy Statement). If Customer collects any User Personal Information from GitHub, Customer will only use it for the purpose for which the External User has authorized it. Customer will reasonably secure any such Personal Information, and Customer will respond promptly to complaints, removal requests, and "do not contact" requests from GitHub or External Users. ### 3.3 Content Responsibility; Ownership; License Rights. @@ -328,13 +328,13 @@ GitHub considers Customer Content in Customer’s Private Repositories to be Cus #### 3.4.3 Access. -GitHub personnel may only access Customer’s Private Repositories in the situations described in our [Privacy Statement](/site-policy/privacy-policies/github-privacy-statement#repository-contents). +GitHub personnel may only access Customer’s Private Repositories in the situations described in our [Privacy Statement](/site-policy/privacy-policies/github-general-privacy-statement#private-repositories-github-access). Customer may choose to enable additional access to its Private Repositories. For example, Customer may enable various GitHub services or features that require additional rights to Customer Content in Private Repositories. These rights may vary depending on the service or feature, but GitHub will continue to treat Customer Content in Customer’s Private Repositories as Customer’s Confidential Information. If those services or features require rights in addition to those it needs to provide the Service, GitHub will provide an explanation of those rights. -Additionally, we may be [compelled by law](/site-policy/privacy-policies/github-privacy-statement#for-legal-disclosure) to disclose the contents of your private repositories. +Additionally, we may be [compelled by law](/site-policy/privacy-policies/github-general-privacy-statement#sharing-of-personal-data) to disclose the contents of your private repositories. -GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/site-policy/privacy-policies/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. +GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/site-policy/privacy-policies/github-general-privacy-statement#sharing-of-personal-data), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. ### 3.5. Intellectual Property Notices. diff --git a/content/site-policy/site-policy-deprecated/github-supplemental-terms-for-microsoft-volume-licensing.md b/content/site-policy/site-policy-deprecated/github-supplemental-terms-for-microsoft-volume-licensing.md index 5930d044f597..39836282141e 100644 --- a/content/site-policy/site-policy-deprecated/github-supplemental-terms-for-microsoft-volume-licensing.md +++ b/content/site-policy/site-policy-deprecated/github-supplemental-terms-for-microsoft-volume-licensing.md @@ -124,7 +124,7 @@ Customer’s use of the Service must comply with [GitHub's Acceptable Use Polici #### 2.2.3 Privacy. -[The GitHub Privacy Statement](/site-policy/privacy-policies/github-privacy-statement) and the [GitHub Data Protection Addendum](https://github.com/customer-terms) provide detailed notice of GitHub's privacy and data use practices as well as GitHub's processing and security obligations with respect to Customer Personal Data. Any person, entity, or service collecting data from the Service must comply with the [GitHub Privacy Statement](/site-policy/privacy-policies/github-privacy-statement), particularly in regards to the collection of Users' Personal Information (as defined in the GitHub Privacy Statement). If Customer collects any User Personal Information from GitHub, Customer will only use it for the purpose for which the External User has authorized it. Customer will reasonably secure any such Personal Information, and Customer will respond promptly to complaints, removal requests, and "do not contact" requests from GitHub or External Users. +[The GitHub Privacy Statement](/site-policy/privacy-policies/github-general-privacy-statement) and the [GitHub Data Protection Addendum](https://github.com/customer-terms) provide detailed notice of GitHub's privacy and data use practices as well as GitHub's processing and security obligations with respect to Customer Personal Data. Any person, entity, or service collecting data from the Service must comply with the [GitHub Privacy Statement](/site-policy/privacy-policies/github-general-privacy-statement), particularly in regards to the collection of Users' Personal Information (as defined in the GitHub Privacy Statement). If Customer collects any User Personal Information from GitHub, Customer will only use it for the purpose for which the External User has authorized it. Customer will reasonably secure any such Personal Information, and Customer will respond promptly to complaints, removal requests, and "do not contact" requests from GitHub or External Users. ### 2.3 Content Responsibility; Ownership; License Rights. From 51c2ad9280745080a9fa3feb68c275eb88f0f8d2 Mon Sep 17 00:00:00 2001 From: Kevin Heis Date: Thu, 9 Jul 2026 06:42:26 -0700 Subject: [PATCH 14/17] Update redirected internal links in codespaces (#62109) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .../understanding-the-codespace-lifecycle.md | 2 +- .../codespaces/about-codespaces/what-are-codespaces.md | 6 +++--- .../creating-a-codespace-from-a-template.md | 2 +- .../developing-in-a-codespace/deleting-a-codespace.md | 2 +- .../opening-an-existing-codespace.md | 2 +- ...o-owns-and-pays-for-codespaces-in-your-organization.md | 8 ++++---- ...r-disabling-github-codespaces-for-your-organization.md | 4 ++-- .../listing-the-codespaces-in-your-organization.md | 4 ++-- ...-the-cost-of-github-codespaces-in-your-organization.md | 8 ++++---- .../restricting-access-to-machine-types.md | 4 ++-- .../restricting-the-idle-timeout-period.md | 2 +- ...of-organization-billed-codespaces-a-user-can-create.md | 2 +- .../restricting-the-retention-period-for-codespaces.md | 2 +- .../about-github-codespaces-prebuilds.md | 2 +- .../allowing-a-prebuild-to-access-other-repositories.md | 4 ++-- .../prebuilding-your-codespaces/configuring-prebuilds.md | 6 +++--- .../prebuilding-your-codespaces/managing-prebuilds.md | 4 ++-- ...llowing-your-codespace-to-access-a-private-registry.md | 2 +- .../using-github-copilot-in-github-codespaces.md | 4 ++-- .../configuring-automatic-deletion-of-your-codespaces.md | 2 +- .../setting-your-timeout-period-for-github-codespaces.md | 2 +- .../troubleshooting/exporting-changes-to-a-branch.md | 2 +- ...troubleshooting-creation-and-deletion-of-codespaces.md | 2 +- .../troubleshooting/troubleshooting-included-usage.md | 6 +++--- .../troubleshooting/troubleshooting-prebuilds.md | 4 ++-- 25 files changed, 44 insertions(+), 44 deletions(-) diff --git a/content/codespaces/about-codespaces/understanding-the-codespace-lifecycle.md b/content/codespaces/about-codespaces/understanding-the-codespace-lifecycle.md index 43760af6bcd8..cf0aca59023b 100644 --- a/content/codespaces/about-codespaces/understanding-the-codespace-lifecycle.md +++ b/content/codespaces/about-codespaces/understanding-the-codespace-lifecycle.md @@ -64,7 +64,7 @@ If you try to delete a codespace with unpushed git commits, your editor will not Codespaces that have been stopped and remain inactive for a specified period of time will be deleted automatically. By default, inactive codespaces are deleted after 30 days, but you can customize your codespace retention period. For more information, see [AUTOTITLE](/codespaces/setting-your-user-preferences/configuring-automatic-deletion-of-your-codespaces). -If you create a codespace, it will continue to accrue storage charges until it is deleted, irrespective of whether it is active or stopped. For more information, see [AUTOTITLE](/billing/concepts/product-billing/github-codespaces). Deleting a codespace does not reduce the current billable amount for {% data variables.product.prodname_github_codespaces %}, which accumulates during each monthly billing cycle. For more information, see [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage). +If you create a codespace, it will continue to accrue storage charges until it is deleted, irrespective of whether it is active or stopped. For more information, see [AUTOTITLE](/billing/concepts/product-billing/github-codespaces). Deleting a codespace does not reduce the current billable amount for {% data variables.product.prodname_github_codespaces %}, which accumulates during each monthly billing cycle. For more information, see [AUTOTITLE](/billing/how-tos/products/view-productlicense-use). For more information on deleting a codespace, see [AUTOTITLE](/codespaces/developing-in-a-codespace/deleting-a-codespace). diff --git a/content/codespaces/about-codespaces/what-are-codespaces.md b/content/codespaces/about-codespaces/what-are-codespaces.md index 7482e7a2daa8..ec87353d0c7b 100644 --- a/content/codespaces/about-codespaces/what-are-codespaces.md +++ b/content/codespaces/about-codespaces/what-are-codespaces.md @@ -41,7 +41,7 @@ If you create a codespace from an organization-owned repository, use of the code ### Using organization-owned codespaces -Owners of organizations on {% data variables.product.prodname_team %} and {% data variables.product.prodname_enterprise %} plans can pay for their members' and collaborators' use of {% data variables.product.prodname_github_codespaces %}. This applies to codespaces created from repositories owned by the organization. See [AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/choosing-who-owns-and-pays-for-codespaces-in-your-organization). You can set a spending limit for use of {% data variables.product.prodname_github_codespaces %} on your organization or enterprise account. See [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces). +Owners of organizations on {% data variables.product.prodname_team %} and {% data variables.product.prodname_enterprise %} plans can pay for their members' and collaborators' use of {% data variables.product.prodname_github_codespaces %}. This applies to codespaces created from repositories owned by the organization. See [AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/choosing-who-owns-and-pays-for-codespaces-in-your-organization). You can set a spending limit for use of {% data variables.product.prodname_github_codespaces %} on your organization or enterprise account. See [AUTOTITLE](/billing/how-tos/set-up-budgets). If use of a codespace will be billed to an organization or enterprise, this is shown when the codespace is created. See [AUTOTITLE](/codespaces/developing-in-a-codespace/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository). Codespaces that are billed to an organization, or its parent enterprise, are owned by the organization and can be deleted by an organization owner. See [AUTOTITLE](/codespaces/developing-in-a-codespace/deleting-a-codespace#deleting-codespaces-in-your-organization). @@ -59,8 +59,8 @@ See [AUTOTITLE](/codespaces/customizing-your-codespace). ## Billing for {% data variables.product.prodname_codespaces %} -For information on pricing, storage, and usage for {% data variables.product.prodname_github_codespaces %}, see [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces). +For information on pricing, storage, and usage for {% data variables.product.prodname_github_codespaces %}, see [AUTOTITLE](/billing/concepts/product-billing/github-codespaces). {% data reusables.billing.default-over-quota-behavior %} -{% data reusables.codespaces.codespaces-monthly-billing %} For information on how organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_github_codespaces %} for an organization, see [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces). +{% data reusables.codespaces.codespaces-monthly-billing %} For information on how organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_github_codespaces %} for an organization, see [AUTOTITLE](/billing/how-tos/set-up-budgets). diff --git a/content/codespaces/developing-in-a-codespace/creating-a-codespace-from-a-template.md b/content/codespaces/developing-in-a-codespace/creating-a-codespace-from-a-template.md index 6ea31fcbcb44..d8c7ab814cbf 100644 --- a/content/codespaces/developing-in-a-codespace/creating-a-codespace-from-a-template.md +++ b/content/codespaces/developing-in-a-codespace/creating-a-codespace-from-a-template.md @@ -21,7 +21,7 @@ You can start from a blank template, choose from templates maintained by {% data {% ifversion ghec %} > [!NOTE] -> If you have a {% data variables.enterprise.prodname_managed_user %}, you cannot use {% data variables.product.company_short %}'s public templates for {% data variables.product.prodname_github_codespaces %}, because you can only create codespaces that are owned and paid for by your organization or enterprise. For more information, see [AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-user-accounts). +> If you have a {% data variables.enterprise.prodname_managed_user %}, you cannot use {% data variables.product.company_short %}'s public templates for {% data variables.product.prodname_github_codespaces %}, because you can only create codespaces that are owned and paid for by your organization or enterprise. For more information, see [AUTOTITLE](/admin/managing-iam/understanding-iam-for-enterprises/abilities-and-restrictions-of-managed-user-accounts). {% endif %} diff --git a/content/codespaces/developing-in-a-codespace/deleting-a-codespace.md b/content/codespaces/developing-in-a-codespace/deleting-a-codespace.md index 28cbb771a1cb..e6623fe9c068 100644 --- a/content/codespaces/developing-in-a-codespace/deleting-a-codespace.md +++ b/content/codespaces/developing-in-a-codespace/deleting-a-codespace.md @@ -30,7 +30,7 @@ Use the tabs at the top of this article to display instructions for each of thes ## Why you should delete unused codespaces -There are costs associated with storing codespaces. You should therefore delete any codespaces you no longer need. See [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces). +There are costs associated with storing codespaces. You should therefore delete any codespaces you no longer need. See [AUTOTITLE](/billing/concepts/product-billing/github-codespaces). {% data reusables.codespaces.max-number-codespaces %} diff --git a/content/codespaces/developing-in-a-codespace/opening-an-existing-codespace.md b/content/codespaces/developing-in-a-codespace/opening-an-existing-codespace.md index fb4d86758198..d3a41d826796 100644 --- a/content/codespaces/developing-in-a-codespace/opening-an-existing-codespace.md +++ b/content/codespaces/developing-in-a-codespace/opening-an-existing-codespace.md @@ -17,7 +17,7 @@ You can reopen any of your active or stopped codespaces on {% data variables.pro You can view all your codespaces on the "Your codespaces" page at [github.com/codespaces](https://github.com/codespaces). From this page, you can: * Open, stop, or delete your codespaces. -* See who owns (and may be billed for) your codespaces: your personal account, or organizations you belong to. See [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces). +* See who owns (and may be billed for) your codespaces: your personal account, or organizations you belong to. See [AUTOTITLE](/billing/concepts/product-billing/github-codespaces). * See the machine type, size, and status of your codespaces. * Create a new codespace, either by choosing one of {% data variables.product.company_short %}'s templates or by clicking **New codespace**. See [AUTOTITLE](/codespaces/developing-in-a-codespace/creating-a-codespace-from-a-template) and [AUTOTITLE](/codespaces/developing-in-a-codespace/creating-a-codespace-for-a-repository). * Prevent automatic deletion of a codespace. See [AUTOTITLE](/codespaces/setting-your-user-preferences/configuring-automatic-deletion-of-your-codespaces?tool=webui#avoiding-automatic-deletion-of-codespaces). diff --git a/content/codespaces/managing-codespaces-for-your-organization/choosing-who-owns-and-pays-for-codespaces-in-your-organization.md b/content/codespaces/managing-codespaces-for-your-organization/choosing-who-owns-and-pays-for-codespaces-in-your-organization.md index 9d90fa31490e..dfa24b1514a2 100644 --- a/content/codespaces/managing-codespaces-for-your-organization/choosing-who-owns-and-pays-for-codespaces-in-your-organization.md +++ b/content/codespaces/managing-codespaces-for-your-organization/choosing-who-owns-and-pays-for-codespaces-in-your-organization.md @@ -20,11 +20,11 @@ To pay for usage, you must do all of the following things: * Allow at least some of your members and collaborators to use {% data variables.product.prodname_github_codespaces %} in your organization's private {% ifversion ghec %}and internal {% endif %}repositories. See [AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/enabling-or-disabling-github-codespaces-for-your-organization#enabling-or-disabling-github-codespaces). * Choose for codespaces created from your organization's repositories to be **organization-owned**. See [Choosing who owns and pays for codespaces](#choosing-who-owns-and-pays-for-codespaces). -* Set a non-zero spending limit for {% data variables.product.prodname_github_codespaces %}. See [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces#managing-the-github-codespaces-spending-limit-for-your-organization-account). +* Set a non-zero spending limit for {% data variables.product.prodname_github_codespaces %}. See [AUTOTITLE](/billing/how-tos/set-up-budgets#managing-budgets-for-your-organization-or-enterprise). ## About choosing who pays for codespaces -Paying for a codespace means paying for the storage and compute costs of the codespace over the codespace's lifetime. See [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces). +Paying for a codespace means paying for the storage and compute costs of the codespace over the codespace's lifetime. See [AUTOTITLE](/billing/concepts/product-billing/github-codespaces). Organizations on a {% data variables.product.prodname_free_team %} plan cannot pay for {% data variables.product.prodname_github_codespaces %}, so the user who creates the codespace always pays. @@ -41,7 +41,7 @@ For more information about enabling {% data variables.product.prodname_github_co {% ifversion ghec %} > [!NOTE] -> If you own an {% data variables.enterprise.prodname_emu_org %} and do not allow {% data variables.product.prodname_github_codespaces %} to be billed to your organization, members with {% data variables.enterprise.prodname_managed_users %} will not be able to use {% data variables.product.prodname_github_codespaces %}. See [AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-user-accounts). +> If you own an {% data variables.enterprise.prodname_emu_org %} and do not allow {% data variables.product.prodname_github_codespaces %} to be billed to your organization, members with {% data variables.enterprise.prodname_managed_users %} will not be able to use {% data variables.product.prodname_github_codespaces %}. See [AUTOTITLE](/admin/managing-iam/understanding-iam-for-enterprises/abilities-and-restrictions-of-managed-user-accounts). {% endif %} @@ -86,4 +86,4 @@ If you change from **user ownership** to **organization ownership**, existing co {% data reusables.codespaces.codespaces-spending-limit-requirement %} -For information on managing and changing your account's spending limit, see [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces#managing-the-github-codespaces-spending-limit-for-your-organization-account). +For information on managing and changing your account's spending limit, see [AUTOTITLE](/billing/how-tos/set-up-budgets#managing-budgets-for-your-organization-or-enterprise). diff --git a/content/codespaces/managing-codespaces-for-your-organization/enabling-or-disabling-github-codespaces-for-your-organization.md b/content/codespaces/managing-codespaces-for-your-organization/enabling-or-disabling-github-codespaces-for-your-organization.md index 26a08d0034d5..7acc4f0e17dc 100644 --- a/content/codespaces/managing-codespaces-for-your-organization/enabling-or-disabling-github-codespaces-for-your-organization.md +++ b/content/codespaces/managing-codespaces-for-your-organization/enabling-or-disabling-github-codespaces-for-your-organization.md @@ -45,8 +45,8 @@ To allow a user to create codespaces for a repository owned by your organization {% ifversion ghec %} Additionally, ensure that: -* Your enterprise does not use OIDC with CAP. For more information, see [AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy). -* Your organization does not have an IP address allow list enabled. For more information, see [Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization). +* Your enterprise does not use OIDC with CAP. For more information, see [AUTOTITLE](/admin/managing-iam/configuring-authentication-for-enterprise-managed-users/about-support-for-your-idps-conditional-access-policy). +* Your organization does not have an IP address allow list enabled. For more information, see [Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization). {% endif %} diff --git a/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md b/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md index 92784e1bd408..623979a19d90 100644 --- a/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md +++ b/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md @@ -14,11 +14,11 @@ category: ## Overview -As an organization owner, you can list all of the currently active and stopped codespaces for your organization. You might want to do this to check how many codespaces users are creating, to make sure they aren't incurring unnecessary costs. For information about pricing, see [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces). +As an organization owner, you can list all of the currently active and stopped codespaces for your organization. You might want to do this to check how many codespaces users are creating, to make sure they aren't incurring unnecessary costs. For information about pricing, see [AUTOTITLE](/billing/concepts/product-billing/github-codespaces). The easiest way to list the codespaces for an organization is by using {% data variables.product.prodname_cli %}. You can also use the REST API, which provides more information about each codespace. -For information on how to see the current total {% data variables.product.prodname_codespaces %} usage for your organization or enterprise, and generate a detailed report, see [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage). +For information on how to see the current total {% data variables.product.prodname_codespaces %} usage for your organization or enterprise, and generate a detailed report, see [AUTOTITLE](/billing/how-tos/products/view-productlicense-use). ### Using {% data variables.product.prodname_cli %} to list codespaces diff --git a/content/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization.md b/content/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization.md index 55ddbf1ab626..cd10fe27407f 100644 --- a/content/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization.md +++ b/content/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization.md @@ -19,20 +19,20 @@ category: Your organization is billed according to its compute and storage usage for {% data variables.product.prodname_github_codespaces %}. This article explains the ways in which you, as an organization owner, can manage these costs. -To learn about pricing for {% data variables.product.prodname_github_codespaces %}, see [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing). +To learn about pricing for {% data variables.product.prodname_github_codespaces %}, see [AUTOTITLE](/billing/concepts/product-billing/github-codespaces#pricing). ## Spending limits -You can set a spending limit for {% data variables.product.prodname_github_codespaces %} for your organization. This limit is applied to the total compute and storage cost for {% data variables.product.prodname_github_codespaces %}. For more information, see [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces). +You can set a spending limit for {% data variables.product.prodname_github_codespaces %} for your organization. This limit is applied to the total compute and storage cost for {% data variables.product.prodname_github_codespaces %}. For more information, see [AUTOTITLE](/billing/how-tos/set-up-budgets). * **Compute usage:** This is the total time during which all {% data variables.product.prodname_github_codespaces %} instances ("codespaces") were active in a billing month. * **Storage usage:** For {% data variables.product.prodname_github_codespaces %} billing purposes, this includes all files used by all codespaces and prebuilds in your account. This includes resources such as cloned repositories, configuration files, and extensions, among others. -You can check the compute and storage usage for {% data variables.product.prodname_github_codespaces %} for the current billing month. For information, see [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage). +You can check the compute and storage usage for {% data variables.product.prodname_github_codespaces %} for the current billing month. For information, see [AUTOTITLE](/billing/how-tos/products/view-productlicense-use). > [!NOTE] -> Prebuilds for {% data variables.product.prodname_github_codespaces %} are created and updated using {% data variables.product.prodname_actions %}. This may incur billable costs for {% data variables.product.prodname_actions %}. You can set a budget for {% data variables.product.prodname_actions %}. For more information, see [AUTOTITLE](/billing/concepts/product-billing/github-codespaces) and [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions). Storage of the generated prebuilds is charged at the same rate as your codespaces, and is included in your {% data variables.product.prodname_github_codespaces %} budget. +> Prebuilds for {% data variables.product.prodname_github_codespaces %} are created and updated using {% data variables.product.prodname_actions %}. This may incur billable costs for {% data variables.product.prodname_actions %}. You can set a budget for {% data variables.product.prodname_actions %}. For more information, see [AUTOTITLE](/billing/concepts/product-billing/github-codespaces) and [AUTOTITLE](/billing/how-tos/set-up-budgets). Storage of the generated prebuilds is charged at the same rate as your codespaces, and is included in your {% data variables.product.prodname_github_codespaces %} budget. ## Disabling or limiting billing for {% data variables.product.prodname_codespaces %} diff --git a/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md b/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md index a3c33a941fe5..4df5d0df088b 100644 --- a/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md +++ b/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md @@ -16,7 +16,7 @@ category: Typically, when you create a codespace you are offered a choice of specifications for the machine that will run your codespace. You can choose the machine type that best suits your needs. For more information, see [AUTOTITLE](/codespaces/developing-in-a-codespace/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository). -If you pay for using {% data variables.product.prodname_github_codespaces %} then your choice of machine type will affect how much you are billed. The compute cost for a codespace is proportional to the number of processor cores in the machine type you choose. For example, the compute cost of using a codespace for an hour on a 16-core machine is eight times greater than a 2-core machine. For more information about pricing, see [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces). +If you pay for using {% data variables.product.prodname_github_codespaces %} then your choice of machine type will affect how much you are billed. The compute cost for a codespace is proportional to the number of processor cores in the machine type you choose. For example, the compute cost of using a codespace for an hour on a 16-core machine is eight times greater than a 2-core machine. For more information about pricing, see [AUTOTITLE](/billing/concepts/product-billing/github-codespaces). As an organization owner, you may want to configure constraints on the types of machine that are available. For example, if the work in your organization doesn't require significant compute power or storage space, you can remove the highly resourced machines from the list of options that people can choose from. You do this by defining one or more policies in the {% data variables.product.prodname_github_codespaces %} settings for your organization. @@ -83,4 +83,4 @@ You can edit an existing policy. For example, you may want to add or remove cons ## Further reading -* [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces) +* [AUTOTITLE](/billing/how-tos/set-up-budgets) diff --git a/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md b/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md index fbb9d8aefd6e..639af4233055 100644 --- a/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md +++ b/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md @@ -23,7 +23,7 @@ As an organization owner, you may want to configure constraints on the maximum i > [!NOTE] > Maximum idle timeout constraints only apply to codespaces that are owned by your organization. -For more information about pricing for {% data variables.product.prodname_github_codespaces %} compute usage, see [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing). +For more information about pricing for {% data variables.product.prodname_github_codespaces %} compute usage, see [AUTOTITLE](/billing/concepts/product-billing/github-codespaces#pricing). ### Inactivity defined diff --git a/content/codespaces/managing-codespaces-for-your-organization/restricting-the-number-of-organization-billed-codespaces-a-user-can-create.md b/content/codespaces/managing-codespaces-for-your-organization/restricting-the-number-of-organization-billed-codespaces-a-user-can-create.md index ff7ef6080077..740699fd6eee 100644 --- a/content/codespaces/managing-codespaces-for-your-organization/restricting-the-number-of-organization-billed-codespaces-a-user-can-create.md +++ b/content/codespaces/managing-codespaces-for-your-organization/restricting-the-number-of-organization-billed-codespaces-a-user-can-create.md @@ -22,7 +22,7 @@ To restrict the maximum number of organization-billed codespaces that users can This setting does not restrict users from creating codespaces that are not billed to your organization. For example, they can create additional codespaces for public repositories, using their personal {% data variables.product.prodname_codespaces %} usage allowance. However, users who are permitted to create organization-billed codespaces, but have reached the limit for such codespaces, cannot choose to create a codespace for an organization-owned repository using their personal included allowance. -For information about the free use of {% data variables.product.prodname_github_codespaces %} for personal accounts, see [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#monthly-included-storage-and-core-hours-for-personal-accounts). For information on how to choose who can create codespaces that are billed to your organization, see [AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/enabling-or-disabling-github-codespaces-for-your-organization#choose-who-can-create-codespaces-that-are-billed-to-your-organization). +For information about the free use of {% data variables.product.prodname_github_codespaces %} for personal accounts, see [AUTOTITLE](/billing/concepts/product-billing/github-codespaces#free-and-billed-use-by-personal-accounts). For information on how to choose who can create codespaces that are billed to your organization, see [AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/enabling-or-disabling-github-codespaces-for-your-organization#choose-who-can-create-codespaces-that-are-billed-to-your-organization). Policies with the "Maximum codespaces per user" constraint are applied to every repository in your organization. You can't, therefore, add this constraint to an existing policy that is configured to apply only to selected repositories. diff --git a/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md b/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md index e7837a38c56d..eb5be633e70d 100644 --- a/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md +++ b/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md @@ -18,7 +18,7 @@ category: {% data variables.product.prodname_dotcom %} users can set a personal retention period of less than 30 days for codespaces they create. For more information, see [AUTOTITLE](/codespaces/setting-your-user-preferences/configuring-automatic-deletion-of-your-codespaces). -As an organization owner, you may want to configure constraints on the maximum retention period for codespaces created for the repositories owned by your organization. This can help you to limit the storage costs associated with codespaces that are stopped and then left unused until they are automatically deleted. For more information about storage charges, see [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing). You can set a maximum retention period for all, or for specific, repositories owned by your organization. +As an organization owner, you may want to configure constraints on the maximum retention period for codespaces created for the repositories owned by your organization. This can help you to limit the storage costs associated with codespaces that are stopped and then left unused until they are automatically deleted. For more information about storage charges, see [AUTOTITLE](/billing/concepts/product-billing/github-codespaces#pricing). You can set a maximum retention period for all, or for specific, repositories owned by your organization. > [!NOTE] > Setting a maximum retention policy for a repository prevents people from exempting a codespace from automatic deletion. The "Keep codespace" option will be unavailable for codespaces created for that repository. For more information, see [AUTOTITLE](/codespaces/setting-your-user-preferences/configuring-automatic-deletion-of-your-codespaces?tool=webui#avoiding-automatic-deletion-of-codespaces). diff --git a/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md b/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md index 3224c9928fb3..dc5f59decec5 100644 --- a/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md +++ b/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md @@ -35,7 +35,7 @@ To create a prebuild, you set up a prebuild configuration. When you save the con When a prebuild configuration workflow runs, {% data variables.product.prodname_dotcom %} creates a temporary codespace, performing setup operations up to and including any `onCreateCommand` and `updateContentCommand` commands in the `devcontainer.json` file. No `postCreateCommand` commands are run during the creation of a prebuild. For more information about these commands, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation. A snapshot of the generated container is then taken and stored. -As with other {% data variables.product.prodname_actions %} workflows, running a prebuild configuration workflow will either consume some of the {% data variables.product.prodname_actions %} minutes included with your account, if you have any, or it will incur charges for {% data variables.product.prodname_actions %} minutes. Storage of codespace prebuilds is billed in the same way as storage of active or stopped codespaces. For more information, see [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces). +As with other {% data variables.product.prodname_actions %} workflows, running a prebuild configuration workflow will either consume some of the {% data variables.product.prodname_actions %} minutes included with your account, if you have any, or it will incur charges for {% data variables.product.prodname_actions %} minutes. Storage of codespace prebuilds is billed in the same way as storage of active or stopped codespaces. For more information, see [AUTOTITLE](/billing/concepts/product-billing/github-codespaces). When you create a codespace from a prebuild, {% data variables.product.prodname_dotcom %} downloads the existing container snapshot from storage and deploys it on a fresh virtual machine, completing the remaining commands specified in the dev container configuration. Since many operations have already been performed, such as cloning the repository, creating a codespace from a prebuild can be substantially quicker than creating one without a prebuild. This is true where the repository is large and/or `onCreateCommand` commands take a long time to run. diff --git a/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md b/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md index 9b00b2847baa..ab0d35ffc5ba 100644 --- a/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md +++ b/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md @@ -33,7 +33,7 @@ You will need to create a new personal account and then use this account to crea 1. Create a new personal account on {% data variables.product.prodname_dotcom %}. > [!WARNING] - > Although you can generate the {% data variables.product.pat_v1 %} using your existing personal account, we strongly recommend creating a new account with access only to the target repositories required for your scenario. This is because the access token's `repository` permission grants access to all of the repositories that the account has access to. For more information, see [AUTOTITLE](/get-started/start-your-journey/creating-an-account-on-github) and [AUTOTITLE](/actions/security-guides/security-hardening-for-github-actions#considering-cross-repository-access). + > Although you can generate the {% data variables.product.pat_v1 %} using your existing personal account, we strongly recommend creating a new account with access only to the target repositories required for your scenario. This is because the access token's `repository` permission grants access to all of the repositories that the account has access to. For more information, see [AUTOTITLE](/get-started/start-your-journey/creating-an-account-on-github) and [AUTOTITLE](/actions/reference/security/secure-use#allowing-workflows-to-access-internal-and-private-repositories). 1. Give the new account read access to the required repositories. For more information, see [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/managing-an-individuals-access-to-an-organization-repository). 1. While signed into the new account, create a {% data variables.product.pat_v1 %} with the `repo` scope. Optionally, if the prebuild will need to download packages from the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}, also select the `read:packages` scope. For more information, see [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens). @@ -42,7 +42,7 @@ You will need to create a new personal account and then use this account to crea If the prebuild will use a package from the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}, you will need to either grant the new account access to the package or configure the package to inherit the access permissions of the repository you are prebuilding. For more information, see [AUTOTITLE](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility). {% ifversion ghec %} -1. Click **Configure SSO** and authorize the token for use with SAML single sign-on (SSO), so that it can access repositories that are owned by organizations with SSO enabled. For more information, see [AUTOTITLE](/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on). +1. Click **Configure SSO** and authorize the token for use with SAML single sign-on (SSO), so that it can access repositories that are owned by organizations with SSO enabled. For more information, see [AUTOTITLE](/authentication/authenticating-with-single-sign-on/authorizing-a-personal-access-token-for-use-with-single-sign-on). ![Screenshot of the "{% data variables.product.pat_v1_caps_plural %}" page. The "Configure SSO" button for a PAT is highlighted with a dark orange outline.](/assets/images/help/codespaces/configure-sso-for-pat.png) diff --git a/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md b/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md index df0451772197..a8eb0766e7f3 100644 --- a/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md +++ b/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md @@ -27,7 +27,7 @@ You can set up prebuilds in any repository owned by a personal account. The preb > [!NOTE] > {% data reusables.codespaces.prebuilds-billing-for-forks %} See [AUTOTITLE](/billing/concepts/product-billing/github-codespaces#how-costs-are-assigned-to-a-billable-account). -For repositories owned by an organization, you can set up prebuilds if the organization is on a {% data variables.product.prodname_team %} or {% data variables.product.prodname_enterprise %} plan. Additionally, you must have added a payment method and set a spending limit for {% data variables.product.prodname_github_codespaces %} on the organization account or its parent enterprise. See [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces#managing-the-github-codespaces-spending-limit-for-your-organization-account) and [AUTOTITLE](/get-started/learning-about-github/githubs-plans). +For repositories owned by an organization, you can set up prebuilds if the organization is on a {% data variables.product.prodname_team %} or {% data variables.product.prodname_enterprise %} plan. Additionally, you must have added a payment method and set a spending limit for {% data variables.product.prodname_github_codespaces %} on the organization account or its parent enterprise. See [AUTOTITLE](/billing/how-tos/set-up-budgets#managing-budgets-for-your-organization-or-enterprise) and [AUTOTITLE](/get-started/learning-about-github/githubs-plans). ## Configuring prebuilds @@ -83,14 +83,14 @@ For repositories owned by an organization, you can set up prebuilds if the organ If you set the number of prebuild versions to save to 1, {% data variables.product.prodname_github_codespaces %} will only save the latest version of the prebuild and will delete the older version each time the template is updated. This means you will not get a prebuilt codespace if you go back to an older dev container configuration. - There is a storage cost associated with each prebuild version that's retained. For example, if you are generating prebuilds in 4 regions and retaining 2 versions, you will be charged for storage of up to 8 prebuilds. See [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing). + There is a storage cost associated with each prebuild version that's retained. For example, if you are generating prebuilds in 4 regions and retaining 2 versions, you will be charged for storage of up to 8 prebuilds. See [AUTOTITLE](/billing/concepts/product-billing/github-codespaces#pricing). 1. Optionally, add users or teams to notify when the prebuild workflow run fails for this configuration. You can begin typing a username, team name, or full name, then click the name once it appears to add them to the list. The users or teams you add will receive an email when prebuild failures occur, containing a link to the workflow run logs to help with further investigation. ![Screenshot of the "Failure notifications" setting. The team named "octocat-team" has been added.](/assets/images/help/codespaces/prebuilds-failure-notification-setting.png) > [!NOTE] - > People will only receive notifications of failed prebuilds if they have enabled notifications for failed Actions workflows in their personal settings. See [AUTOTITLE](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#github-actions-notification-options). + > People will only receive notifications of failed prebuilds if they have enabled notifications for failed Actions workflows in their personal settings. See [AUTOTITLE](/actions/concepts/workflows-and-actions/notifications-for-workflow-runs). 1. Optionally, at the bottom of the page, click **Show advanced options**. diff --git a/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md b/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md index c14994b44fbd..cc1f6bf8ace1 100644 --- a/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md +++ b/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md @@ -27,7 +27,7 @@ The settings in the prebuild configuration determine which events automatically People with admin access to a repository can check the progress of prebuilds, edit, and delete prebuild configurations. -To locate all repositories that are hosting a prebuild configuration, you must obtain a copy of your usage report by following the steps for [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage). +To locate all repositories that are hosting a prebuild configuration, you must obtain a copy of your usage report by following the steps for [AUTOTITLE](/billing/how-tos/products/view-productlicense-use). ## Viewing the progress of prebuilds @@ -76,7 +76,7 @@ Disabling the workflow runs for a prebuild configuration is useful if you need t ## Deleting a prebuild configuration > [!NOTE] -> You can find a list of the repositories that contain a prebuild by obtaining a copy of your “[usage report](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage).” +> You can find a list of the repositories that contain a prebuild by obtaining a copy of your “[usage report](/billing/how-tos/products/view-productlicense-use).” Deleting a prebuild configuration also deletes all previously created prebuilds for that configuration. As a result, shortly after you delete a configuration, prebuilds generated by that configuration will no longer be available when you create a new codespace. diff --git a/content/codespaces/reference/allowing-your-codespace-to-access-a-private-registry.md b/content/codespaces/reference/allowing-your-codespace-to-access-a-private-registry.md index 33954c4f447e..91c9097338ee 100644 --- a/content/codespaces/reference/allowing-your-codespace-to-access-a-private-registry.md +++ b/content/codespaces/reference/allowing-your-codespace-to-access-a-private-registry.md @@ -52,7 +52,7 @@ If you want to allow a subset of an organization's repositories to access a pack Seamless access from a codespace to a registry is limited to pulling packages. If you want to publish a package from inside a codespace, you must use a {% data variables.product.pat_v1 %} with the `write:packages` scope. -We recommend publishing packages via {% data variables.product.prodname_actions %}. For more information, see [AUTOTITLE](/actions/publishing-packages/publishing-docker-images) and [AUTOTITLE](/actions/publishing-packages/publishing-nodejs-packages). +We recommend publishing packages via {% data variables.product.prodname_actions %}. For more information, see [AUTOTITLE](/actions/tutorials/publish-packages/publish-docker-images) and [AUTOTITLE](/actions/tutorials/publish-packages/publish-nodejs-packages). ## Accessing images stored in other registries diff --git a/content/codespaces/reference/using-github-copilot-in-github-codespaces.md b/content/codespaces/reference/using-github-copilot-in-github-codespaces.md index 732fe0ea21e8..f16f89c63f8f 100644 --- a/content/codespaces/reference/using-github-copilot-in-github-codespaces.md +++ b/content/codespaces/reference/using-github-copilot-in-github-codespaces.md @@ -14,7 +14,7 @@ category: - Write code in a codespace --- -[{% data variables.product.prodname_copilot %}](https://copilot.github.com/) is an AI pair programmer that you can use in any codespace that you open in the {% data variables.product.prodname_vscode_shortname %} web client or desktop application. For more information about {% data variables.product.prodname_copilot %}, see [AUTOTITLE](/copilot/about-github-copilot/what-is-github-copilot). +[{% data variables.product.prodname_copilot %}](https://copilot.github.com/) is an AI pair programmer that you can use in any codespace that you open in the {% data variables.product.prodname_vscode_shortname %} web client or desktop application. For more information about {% data variables.product.prodname_copilot %}, see [AUTOTITLE](/copilot/get-started/what-is-github-copilot). To start using {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_github_codespaces %}, install the [{% data variables.product.prodname_copilot %} extension from the {% data variables.product.prodname_vscode_marketplace %}](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot). @@ -22,4 +22,4 @@ To include {% data variables.product.prodname_copilot %}, or other extensions, i ## Further reading -* [AUTOTITLE](/copilot/quickstart) +* [AUTOTITLE](/copilot/get-started/quickstart) diff --git a/content/codespaces/setting-your-user-preferences/configuring-automatic-deletion-of-your-codespaces.md b/content/codespaces/setting-your-user-preferences/configuring-automatic-deletion-of-your-codespaces.md index 3c30a2967100..433069a9154c 100644 --- a/content/codespaces/setting-your-user-preferences/configuring-automatic-deletion-of-your-codespaces.md +++ b/content/codespaces/setting-your-user-preferences/configuring-automatic-deletion-of-your-codespaces.md @@ -14,7 +14,7 @@ category: By default, {% data variables.product.prodname_github_codespaces %} are automatically deleted after they have been stopped and have remained inactive for 30 days. -However, because {% data variables.product.prodname_github_codespaces %} incurs storage charges, you may prefer to reduce the retention period by changing your default period in your personal settings for {% data variables.product.prodname_github_codespaces %}. For more information about storage charges, see [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing). +However, because {% data variables.product.prodname_github_codespaces %} incurs storage charges, you may prefer to reduce the retention period by changing your default period in your personal settings for {% data variables.product.prodname_github_codespaces %}. For more information about storage charges, see [AUTOTITLE](/billing/concepts/product-billing/github-codespaces#pricing). > [!NOTE] > Whether or not you have set a personal codespace retention period, it's a good idea to get into the habit of deleting codespaces that you no longer need. See [AUTOTITLE](/codespaces/developing-in-a-codespace/deleting-a-codespace). diff --git a/content/codespaces/setting-your-user-preferences/setting-your-timeout-period-for-github-codespaces.md b/content/codespaces/setting-your-user-preferences/setting-your-timeout-period-for-github-codespaces.md index a8c12d0d0762..c240ac25a588 100644 --- a/content/codespaces/setting-your-user-preferences/setting-your-timeout-period-for-github-codespaces.md +++ b/content/codespaces/setting-your-user-preferences/setting-your-timeout-period-for-github-codespaces.md @@ -18,7 +18,7 @@ category: A codespace will stop running after a period of inactivity. By default this period is 30 minutes, but you can specify a longer or shorter default timeout period in your personal settings on {% data variables.product.prodname_dotcom %}. The updated setting will apply to any new codespaces you create. You can also specify a timeout when you use {% data variables.product.prodname_cli %} to create a codespace. > [!WARNING] -> Codespaces compute usage is billed for the duration for which a codespace is active. If you're not using a codespace but it remains running, and hasn't yet timed out, you are billed for the total time that the codespace was active, irrespective of whether you were using it. For more information, see [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing). +> Codespaces compute usage is billed for the duration for which a codespace is active. If you're not using a codespace but it remains running, and hasn't yet timed out, you are billed for the total time that the codespace was active, irrespective of whether you were using it. For more information, see [AUTOTITLE](/billing/concepts/product-billing/github-codespaces#pricing). ### Inactivity defined diff --git a/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md b/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md index 30b1e0bc2b4b..e850ebf515e9 100644 --- a/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md +++ b/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md @@ -12,7 +12,7 @@ category: ## About exporting changes -While using {% data variables.product.prodname_github_codespaces %}, you may want to export your changes to a branch without launching your codespace. This can be useful when you have hit a [spending limit](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces) or have a general issue accessing your codespace. +While using {% data variables.product.prodname_github_codespaces %}, you may want to export your changes to a branch without launching your codespace. This can be useful when you have hit a [spending limit](/billing/how-tos/set-up-budgets) or have a general issue accessing your codespace. You can export your changes in one of several ways, depending on how you created the codespace. In every case, only the Git branch that is currently checked out in the codespace is exported. Work contained in other branches is not exported. diff --git a/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md b/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md index 7bcceea7b381..93150f3e02eb 100644 --- a/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md +++ b/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md @@ -27,7 +27,7 @@ If you can't create a codespace for a repository, this may be due to one of the For information about other organization and enterprise settings that can affect whether you can create a codespace, see [AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/enabling-or-disabling-github-codespaces-for-your-organization#prerequisites-for-enabling-github-codespaces). -For more information about included usage for personal accounts, and setting a spending limit, see [AUTOTITLE](/free-pro-team@latest/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces) and [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces). +For more information about included usage for personal accounts, and setting a spending limit, see [AUTOTITLE](/free-pro-team@latest/billing/concepts/product-billing/github-codespaces) and [AUTOTITLE](/billing/how-tos/set-up-budgets). ### Codespace does not open when created diff --git a/content/codespaces/troubleshooting/troubleshooting-included-usage.md b/content/codespaces/troubleshooting/troubleshooting-included-usage.md index 2becdafc129b..087964fcc8b0 100644 --- a/content/codespaces/troubleshooting/troubleshooting-included-usage.md +++ b/content/codespaces/troubleshooting/troubleshooting-included-usage.md @@ -35,7 +35,7 @@ You can see the storage usage for each of your codespaces on the "Your codespace > [!NOTE] > If the dev container for a codespace was built from the default image, the size of the codespace shown on this page does not include the size of the base dev container. Storage for the base dev container is provided free of charge. See [Storage usage for your base dev container](#storage-usage-for-your-base-dev-container). -For billing purposes, {% data variables.product.prodname_codespaces %} storage is counted in GB-hours. See [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces). +For billing purposes, {% data variables.product.prodname_codespaces %} storage is counted in GB-hours. See [AUTOTITLE](/billing/concepts/product-billing/github-codespaces). ### Where did my monthly storage go? @@ -45,13 +45,13 @@ Although prebuilds are not listed on the "Your codespaces" page, prebuilds creat ## Understanding your {% data variables.product.prodname_codespaces %} usage -You can check the cumulative {% data variables.product.prodname_github_codespaces %} usage for your current monthly billing cycle in your {% data variables.product.prodname_dotcom %} settings. See [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage). +You can check the cumulative {% data variables.product.prodname_github_codespaces %} usage for your current monthly billing cycle in your {% data variables.product.prodname_dotcom %} settings. See [AUTOTITLE](/billing/how-tos/products/view-productlicense-use). ![Screenshot of the "{% data variables.product.prodname_codespaces %}" section of the billing page showing figures for "Usage hours" and "Storage."](/assets/images/help/codespaces/view-personal-usage-collapsed.png) You can expand the "Usage hours" and "Storage" section for more information - for example, to see how much of the consumed storage was used by prebuilds. -For more specific information - for example, if you want to know which repositories have prebuilds that are consuming storage - you can generate a usage report. The usage report is a CSV file that's emailed to you. For more information on how to generate a usage report, see [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage). +For more specific information - for example, if you want to know which repositories have prebuilds that are consuming storage - you can generate a usage report. The usage report is a CSV file that's emailed to you. For more information on how to generate a usage report, see [AUTOTITLE](/billing/how-tos/products/view-productlicense-use). To see your {% data variables.product.prodname_codespaces %} usage, filter the report to show only rows that mention "Codespaces" in the `Product` column. diff --git a/content/codespaces/troubleshooting/troubleshooting-prebuilds.md b/content/codespaces/troubleshooting/troubleshooting-prebuilds.md index 5486e0bbc715..8cfe37b24024 100644 --- a/content/codespaces/troubleshooting/troubleshooting-prebuilds.md +++ b/content/codespaces/troubleshooting/troubleshooting-prebuilds.md @@ -42,7 +42,7 @@ cat /workspaces/.codespaces/shared/environment-variables.json | jq '.ACTION_NAME You can check whether a repository is using prebuilds in the "{% data variables.product.prodname_codespaces %}" page of the repository's settings. -You can check how much storage space has been consumed by prebuilds in your current billing cycle by reviewing the billing data for your personal or organization account. You can also generate a usage report to see which repositories have been using prebuilds. For more information, see [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage). +You can check how much storage space has been consumed by prebuilds in your current billing cycle by reviewing the billing data for your personal or organization account. You can also generate a usage report to see which repositories have been using prebuilds. For more information, see [AUTOTITLE](/billing/how-tos/products/view-productlicense-use). ## The "Prebuild Ready" label is sometimes missing @@ -67,7 +67,7 @@ If the `devcontainer.json` configuration file for a prebuild configuration speci ### Increasing the {% data variables.product.prodname_actions %} spending limit -Prebuilds are created and updated using {% data variables.product.prodname_actions %}. Your prebuild workflows will fail if you have used all of your {% data variables.product.prodname_actions %} minutes and have reached your spending limit. If this occurs you can increase your {% data variables.product.prodname_actions %} spending limit to allow the workflows to run. For more information, see [AUTOTITLE](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions). +Prebuilds are created and updated using {% data variables.product.prodname_actions %}. Your prebuild workflows will fail if you have used all of your {% data variables.product.prodname_actions %} minutes and have reached your spending limit. If this occurs you can increase your {% data variables.product.prodname_actions %} spending limit to allow the workflows to run. For more information, see [AUTOTITLE](/billing/how-tos/set-up-budgets). ### Authorizing access permissions From 10d4c89be9111abf4690d099c99af8ef5b56605b Mon Sep 17 00:00:00 2001 From: Kevin Heis Date: Thu, 9 Jul 2026 06:42:33 -0700 Subject: [PATCH 15/17] Step webapp maxSurge 25% -> 50% to speed deploys (#62179) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- config/kubernetes/production/deployments/webapp.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config/kubernetes/production/deployments/webapp.yaml b/config/kubernetes/production/deployments/webapp.yaml index 04ff6cf53ff0..f494d099cfae 100644 --- a/config/kubernetes/production/deployments/webapp.yaml +++ b/config/kubernetes/production/deployments/webapp.yaml @@ -14,7 +14,7 @@ spec: # Prevents capacity loss during deploys. Safe because we're over-provisioned. maxUnavailable: 0 # Percentage so it scales with replica count changes. - maxSurge: '25%' + maxSurge: '50%' selector: matchLabels: app: webapp From 9327df3a4a45619de8d19fc85d22e1d3e1a84255 Mon Sep 17 00:00:00 2001 From: Kevin Heis Date: Thu, 9 Jul 2026 06:42:41 -0700 Subject: [PATCH 16/17] Emit fine-grained surrogate keys on content responses (#62180) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .../middleware/set-fastly-surrogate-key.ts | 69 ++++++++++++++++++- src/frame/tests/server.ts | 16 +++++ 2 files changed, 84 insertions(+), 1 deletion(-) diff --git a/src/frame/middleware/set-fastly-surrogate-key.ts b/src/frame/middleware/set-fastly-surrogate-key.ts index a41eb502fef0..172158e57d8d 100644 --- a/src/frame/middleware/set-fastly-surrogate-key.ts +++ b/src/frame/middleware/set-fastly-surrogate-key.ts @@ -1,6 +1,7 @@ import type { Request, Response, NextFunction } from 'express' import { ExtendedRequest } from '@/types' +import type { Page, Version } from '@/types' // Fastly provides a Soft Purge feature that allows you to mark content as outdated (stale) instead of permanently // purging and thereby deleting it from Fastly's caches. Objects invalidated with Soft Purge will be treated as @@ -40,7 +41,13 @@ export function setLanguageFastlySurrogateKey( res: Response, next: NextFunction, ) { - res.set(KEY, makeLanguageSurrogateKey(req.language)) + const context = req.context + const keys = makeContentSurrogateKeys({ + langCode: req.language, + productId: productSurrogateId(context?.page), + versionKey: versionSurrogateKey(context?.currentVersionObj), + }) + res.set(KEY, keys.join(' ')) return next() } @@ -50,3 +57,63 @@ export function makeLanguageSurrogateKey(langCode?: string) { } return `language:${langCode}` } + +// Build the fine-grained surrogate keys for a content response (docs-engineering#6719). +// A content page is exactly one of each axis, so ~4 keys per page, well under +// Fastly's 16 KB Surrogate-Key header limit: +// +// language: (also emitted for non-content responses) +// product: e.g. product:actions (~36) +// version: e.g. version:ghes-3.14 (~7-8) +// product:,language: compound, for targeted translation purges +// +// These keys are inert: nothing purges the new keys yet. docs-engineering#6720 +// will use them to target the tightest key that covers a deploy instead of +// soft-purging a whole language. Space is the Fastly delimiter; colons and +// commas are fine (we already ship `language:en` and `api-search:en`). The +// language key stays first so anything that only reads the first token (e.g. +// the caching-headers test helper) keeps working. +export function makeContentSurrogateKeys({ + langCode, + productId, + versionKey, +}: { + langCode?: string + productId?: string + versionKey?: string +}): string[] { + const keys = [makeLanguageSurrogateKey(langCode)] + if (productId) { + keys.push(`product:${productId}`) + if (langCode) { + keys.push(`product:${productId},language:${langCode}`) + } + } + if (versionKey) { + keys.push(`version:${versionKey}`) + } + return keys +} + +// Derive the product id for the `product:` surrogate key from a content page's +// path. The top-level content directory is the product id (mirrors +// Page.parentProductId), e.g. `actions`. Returns undefined for non-content +// responses and the top-level homepage (`content/index.md`). +function productSurrogateId(page?: Page): string | undefined { + const relativePath = page?.relativePath + if (!relativePath) return undefined + const id = relativePath.split('/')[0] + if (!id || id.endsWith('.md')) return undefined + return id +} + +// Derive the short release slug for the `version:` surrogate key, e.g. `fpt`, +// `ghec`, `ghes-3.14`. Numbered releases (GHES) get the release appended so a +// version-scoped purge can target a single release; unnumbered plans use the +// plain short name. +function versionSurrogateKey(versionObj?: Version): string | undefined { + if (!versionObj) return undefined + return versionObj.hasNumberedReleases + ? `${versionObj.shortName}-${versionObj.currentRelease}` + : versionObj.shortName +} diff --git a/src/frame/tests/server.ts b/src/frame/tests/server.ts index 1dc89b590e98..c602b5952fc9 100644 --- a/src/frame/tests/server.ts +++ b/src/frame/tests/server.ts @@ -75,6 +75,22 @@ describe('server', () => { expect(surrogateKeySplit.includes(makeLanguageSurrogateKey('en'))).toBeTruthy() }) + test('sets fine-grained product and version surrogate keys on content pages', async () => { + // docs-engineering#6719: content pages emit language, product, version, and + // a product,language compound key so per-deploy purges can target the + // tightest key instead of a whole language. + const res = await get('/en/get-started') + expect(res.statusCode).toBe(200) + const keys = res.headers['surrogate-key'].split(/\s/g) + // Language key stays first for anything that only reads the first token. + expect(keys[0]).toBe(makeLanguageSurrogateKey('en')) + expect(keys).toContain('product:get-started') + expect(keys).toContain('product:get-started,language:en') + expect(keys.some((key: string) => /^version:.+/.test(key))).toBe(true) + // Stays well under Fastly's limits: about 4 keys per page. + expect(keys.length).toBeLessThanOrEqual(6) + }) + test('does not render duplicate or tags', async () => { const $ = await getDOM('/en') expect($('html').length).toBe(1) From 8477db5b2441da9798de92279b98622b87fb5d39 Mon Sep 17 00:00:00 2001 From: Vanessa Date: Fri, 10 Jul 2026 01:01:44 +1000 Subject: [PATCH 17/17] [2026-07-09] Improved repo exploration with Copilot Chat (#61845) Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Co-authored-by: vgrltwin Co-authored-by: Sheena Ganju --- .../get-started-with-chat.md | 12 ++++++++- .../copilot/tutorials/explore-a-codebase.md | 27 +++++++++++++++---- .../tutorials/explore-pull-requests.md | 15 +++++++++++ 3 files changed, 48 insertions(+), 6 deletions(-) diff --git a/content/copilot/how-tos/copilot-on-github/chat-with-copilot/get-started-with-chat.md b/content/copilot/how-tos/copilot-on-github/chat-with-copilot/get-started-with-chat.md index 6b8bbd22dfae..2273c0bc61cc 100644 --- a/content/copilot/how-tos/copilot-on-github/chat-with-copilot/get-started-with-chat.md +++ b/content/copilot/how-tos/copilot-on-github/chat-with-copilot/get-started-with-chat.md @@ -23,9 +23,11 @@ category: ## Repository questions -Navigate to a repository to ask about its code, structure, or history. +Navigate to a repository to ask about its purpose, structure, code, or history. {% data variables.copilot.copilot_chat_short %} grounds its answers in the actual files and symbols in the repository, so you can get a high-level overview and then ask follow-up questions within the same context. * {% prompt %}What is the main purpose of this repo?{% endprompt %} +* {% prompt %}Give me an overview of how this project is structured.{% endprompt %} +* {% prompt %}How do I set up and run this project locally?{% endprompt %} * {% prompt %}Where is rate limiting implemented in our API?{% endprompt %} * {% prompt %}What was the last merged PR by USERNAME{% endprompt %} @@ -47,6 +49,14 @@ Navigate to a pull request to ask about changes, reviews, or failing workflows. * {% prompt %}What did {% data variables.product.prodname_copilot_short %} change in this PR and why?{% endprompt %} * {% prompt %}What did {% data variables.product.prodname_copilot_short %} validate before opening this PR?{% endprompt %} +## Debugging questions + +Navigate to a failed workflow run, a pull request with a failing check, or paste a stack trace to get help diagnosing and fixing the problem. + +* {% prompt %}Why did this workflow run fail?{% endprompt %} +* {% prompt %}Explain this stack trace and suggest a fix.{% endprompt %} +* {% prompt %}Which change in this PR most likely caused the failing test?{% endprompt %} + ## Security alert questions Navigate to a {% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_secret_scanning %}, or {% data variables.product.prodname_dependabot %} alert to ask about it. diff --git a/content/copilot/tutorials/explore-a-codebase.md b/content/copilot/tutorials/explore-a-codebase.md index 7881f5d1bf40..78c5a17cee55 100644 --- a/content/copilot/tutorials/explore-a-codebase.md +++ b/content/copilot/tutorials/explore-a-codebase.md @@ -9,7 +9,7 @@ redirect_from: - /copilot/tutorials/using-copilot-to-explore-a-codebase contentType: tutorials category: - - Scale institutional knowledge + - Scale institutional knowledge - Author and optimize with Copilot --- @@ -21,15 +21,28 @@ If you've been assigned to work on a project that you're not familiar with—or Throughout this guide, we'll work with {% data variables.copilot.copilot_chat_short %} on {% data variables.product.prodname_dotcom_the_website %}, which you can find at [github.com/copilot](https://github.com/copilot?ref_product=copilot&ref_type=engagement&ref_style=text). -## Attaching a codebase +## Providing repository context -Before {% data variables.copilot.copilot_chat_short %} can help you, you need to attach the codebase you want to explore. +You can ask {% data variables.copilot.copilot_chat_short %} about a codebase in either of these ways. + +### Attaching a repository in chat + +Attaching a repository gives {% data variables.copilot.copilot_chat_short %} access to the code in the repository, and is best when you want to compare or switch between repositories during a conversation. 1. On {% data variables.product.github %}, navigate to [github.com/copilot](https://github.com/copilot?ref_product=copilot&ref_type=engagement&ref_style=text). 1. In the text box, click **{% octicon "plus" aria-label="Add attachments" %} Add repositories, files, and spaces**, then click **Repositories**. 1. Search for and select the repository you want to explore. -{% data variables.copilot.copilot_chat_short %} now has access to the code in that repository, and you can start asking questions about it. +### Asking from the repository page + +> [!NOTE] +> This feature is currently in {% data variables.release-phases.public_preview %} and subject to change. + +You can ask {% data variables.copilot.copilot_chat_short %} about a repository directly from its page on {% data variables.product.github %}, without attaching it first. This is a quick way to get oriented in a project you haven't worked on before. + +1. On {% data variables.product.github %}, navigate to the repository you want to explore. +1. Open {% data variables.copilot.copilot_chat_short %} from the repository page and ask a question. {% data variables.product.prodname_copilot_short %} uses the repository as context and grounds its answers in the repository's actual files and symbols. +1. Ask a follow-up question to go deeper, using the same shared context. ## Example prompts @@ -41,6 +54,10 @@ The following prompts are examples of the kind of questions you can ask {% data * `Based on the code in this repository, give me an overview of the architecture of the codebase. Provide evidence.` +* `Give me an overview of this repository: its purpose, structure, key components, and how to run it.` + +* `What are the main entry points and how do the key components fit together?` + * `Which languages are used in this repo? Show the percentages for each language.` * `What are the core algorithms implemented in this repo?` @@ -104,7 +121,7 @@ Use {% data variables.product.prodname_copilot_short %} to help you understand t 1. On {% data variables.product.github %}, navigate to a repository and open a file. 1. At the top of the file, click the {% data variables.product.prodname_copilot_short %} icon (**{% octicon "copilot" aria-label="Copilot icon" %}**) to open {% data variables.copilot.copilot_chat_short %}. - + {% data variables.product.prodname_copilot_short %} will display the file contents in a split screen as context for your question. 1. If you want to ask about a specific symbol, highlight the symbol in the file. diff --git a/content/copilot/tutorials/explore-pull-requests.md b/content/copilot/tutorials/explore-pull-requests.md index 9927407cbcae..47afb3e2c7ea 100644 --- a/content/copilot/tutorials/explore-pull-requests.md +++ b/content/copilot/tutorials/explore-pull-requests.md @@ -34,6 +34,18 @@ The following prompts are examples of the kind of questions you can ask {% data * `What is the current status of this pull request?` * `What are the main changes in this pull request?` +## Ask {% data variables.product.prodname_copilot_short %} to explain changes in a pull request + +You can ask {% data variables.product.prodname_copilot_short %} to examine the changes in a pull request and provide insights. {% data variables.product.prodname_copilot_short %} can return a story of the commits made, a list of unresolved feedback, or assistance with performing a structured review with insights and actionable suggestions, using context from the pull request's file changes, commits, comments, and existing reviews. + +1. On {% data variables.product.github %}, navigate to a pull request in a repository. +1. Open {% data variables.copilot.copilot_chat_short %}, type your question, and press Enter. + +### Example prompts +* `Help me understand the commits made in this pull request.` +* `Is there any unresolved feedback in this pull request?` +* `Help review this pull request.` + ## Ask about changes to a specific file in a pull request You can ask {% data variables.product.prodname_copilot_short %} to explain the changes made to a specific file in a pull request, or to provide information about the status of a file in a pull request. @@ -43,6 +55,8 @@ You can ask {% data variables.product.prodname_copilot_short %} to explain the c 1. To the right side of a line in the file you want to ask about, click the {% octicon "triangle-down" aria-hidden="true" aria-label="Show file actions" %} icon, then click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}**, and select **Ask about this diff**. This opens {% data variables.copilot.copilot_chat_short %} with the file changes indicated as the context of your question. + + Your conversation appears alongside the diff, so you can review the code and chat at the same time. 1. Type a question in the prompt box at the bottom of the chat panel and press Enter. ### Example prompts @@ -96,3 +110,4 @@ When you view a pull request created by {% data variables.copilot.copilot_cloud_ ## Further reading * [AUTOTITLE](/copilot/tutorials/using-copilot-to-explore-a-codebase) +* [AUTOTITLE](/copilot/tutorials/roll-out-at-scale/drive-downstream-impact/accelerate-pull-requests)