diff --git a/assets/images/help/copilot/copilot-icon-top-right.png b/assets/images/help/copilot/copilot-icon-top-right.png new file mode 100644 index 000000000000..24f3f193ae58 Binary files /dev/null and b/assets/images/help/copilot/copilot-icon-top-right.png differ diff --git a/content/get-started/exploring-projects-on-github/contributing-to-a-project.md b/content/get-started/exploring-projects-on-github/contributing-to-a-project.md index a56b9cb68003..4cead07e91c2 100644 --- a/content/get-started/exploring-projects-on-github/contributing-to-a-project.md +++ b/content/get-started/exploring-projects-on-github/contributing-to-a-project.md @@ -18,13 +18,13 @@ redirect_from: ## About forking -If you want to contribute to someone else's project but don't have write access to the repository, you can use a "fork and pull request" workflow. +If you want to contribute to someone else's project but don’t have permission to make changes directly, you can create your own copy of the project, make updates, and then suggest those updates for inclusion in the main project. This process is often called a "fork and pull request" workflow. -{% data reusables.repositories.fork-definition-long %} +When you create your own copy (or "fork") of a project, it’s like making a new workspace that shares code with the original project. This is useful for open-source projects or anytime you don’t have write access to the original project. -You can contribute by submitting pull requests from your fork to the upstream repository. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo)." +Once you’ve made your changes in your copy, you can submit them as a pull request, which is a way to propose changes back to the main project. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo)." -## Forking a repository +## Creating your own copy of a project This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Knife), a test repository that's hosted on {% data variables.product.prodname_dotcom %} that lets you test the fork and pull request workflow. @@ -44,7 +44,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn > [!NOTE] > If you want to copy additional branches from the upstream repository, you can do so from the **Branches** page. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)." -## Cloning a fork +## Cloning a fork to your computer You've successfully forked the Spoon-Knife repository, but so far, it only exists on {% data variables.product.product_name %}. To be able to work on the project, you will need to clone it to your computer. @@ -99,7 +99,7 @@ gh repo fork REPOSITORY --clone=true ## Creating a branch to work on -Before making changes to the project, you should create a new branch and check it out. By keeping changes in their own branch, you follow GitHub Flow and ensure that it will be easier to contribute to the same project again in the future. For more information, see "[AUTOTITLE](/get-started/using-github/github-flow#following-github-flow)." +Before making changes to the project, you should create a new branch and check it out. By keeping changes in their own branch, you follow {% data variables.product.github %} flow and ensure that it will be easier to contribute to the same project again in the future. See "[AUTOTITLE](/get-started/using-github/github-flow#following-github-flow)." {% webui %} @@ -127,7 +127,7 @@ For more information about how to create and manage branches in {% data variable ## Making and pushing changes -Go ahead and make a few changes to the project using your favorite text editor, like [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com). You could, for example, change the text in `index.html` to add your GitHub username. +Go ahead and make a few changes to the project using your favorite text editor, like [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com). You could, for example, change the text in `index.html` to add your {% data variables.product.github %} username. When you're ready to submit your changes, stage and commit your changes. `git add .` tells Git that you want to include all of your changes in the next commit. `git commit` takes a snapshot of those changes. @@ -199,3 +199,9 @@ Pull requests are an area for discussion. Don't be offended if the project owner You've successfully forked and contributed back to a repository. Go forth, and contribute some more!{% ifversion fpt %} For more information, see "[AUTOTITLE](/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github)."{% endif %} + +{% ifversion copilot %} + +## Familiarizing yourself with a project + +If you're new to a project, you can use {% data variables.product.prodname_copilot_short %} to help you understand the purpose of the repository, examine files, and dive into specific lines of code. See "[AUTOTITLE](/get-started/exploring-projects-on-github/using-github-copilot-to-explore-projects)."{% endif %} diff --git a/content/get-started/exploring-projects-on-github/index.md b/content/get-started/exploring-projects-on-github/index.md index aa32d323f90a..4589eb3fd40a 100644 --- a/content/get-started/exploring-projects-on-github/index.md +++ b/content/get-started/exploring-projects-on-github/index.md @@ -15,6 +15,7 @@ topics: - Projects children: - /finding-ways-to-contribute-to-open-source-on-github + - /using-github-copilot-to-explore-projects - /contributing-to-a-project - /saving-repositories-with-stars - /following-people diff --git a/content/get-started/exploring-projects-on-github/using-github-copilot-to-explore-projects.md b/content/get-started/exploring-projects-on-github/using-github-copilot-to-explore-projects.md new file mode 100644 index 000000000000..ac3837d15968 --- /dev/null +++ b/content/get-started/exploring-projects-on-github/using-github-copilot-to-explore-projects.md @@ -0,0 +1,45 @@ +--- +title: Using GitHub Copilot to explore projects +intro: 'This guide will help you use {% data variables.product.prodname_copilot_short %} to explore projects on {% data variables.product.prodname_dotcom %}.' +versions: + feature: copilot +topics: + - Copilot + - Repositories +shortTitle: Use Copilot to explore projects +--- + +> [!NOTE] {% data variables.product.prodname_copilot_chat_dotcom %} is currently in {% data variables.release-phases.public_preview %} and is subject to change. + +In this guide, you’ll learn how to use {% data variables.product.prodname_copilot_chat_dotcom_short %} to understand a repository’s purpose, examine files, and dive into specific lines of code. By following these steps, you’ll gain insights into any project faster—making onboarding, code review, and project exploration easier and more efficient. + +## Prerequisites + +{% data reusables.copilot.copilot-requires-subscription %} + +## Understanding a repository + +When you’re new to a project, it can be challenging to understand the purpose of a repository and its files. {% data variables.product.prodname_copilot_short %} can help you quickly understand the purpose of a repository, for example, by providing a summary of the repository’s README file. + +1. On the {% data variables.product.prodname_dotcom %} website, go to the repository you want to chat about. + +1. Click the **{% octicon "copilot" aria-hidden="true" %}** {% data variables.product.prodname_copilot %} icon at the top right of the page. +1. The heading at the top of the chat panel should read "Chatting about" followed by the name of the current repository. + + If the wrong repository name is displayed, because you were previously chatting about another repository, click **All repositories** then choose the repository you want to chat about. + + ![Screenshot of the {% data variables.product.prodname_copilot_short %} chat panel page with "All repositories" highlighted with a dark orange outline.](/assets/images/help/copilot/copilot-chat-all-repositories.png) + +1. In the "Ask {% data variables.product.prodname_copilot_short %}" box, at the bottom of the chat panel, type "Summarize the purpose of this repository based on the README" and press Enter. {% data variables.product.prodname_copilot_short %} replies in the chat panel. + +You can also use {% data variables.product.prodname_copilot_short %} to understand the roles of different folders and files within the repository. For example, you can ask {% data variables.product.prodname_copilot_short %} to summarize the contents of a specific file, or to explain the purpose of a specific folder. + +## Exploring files and code + +When you’re exploring a project, you might want to understand the contents of a specific file. {% data variables.product.prodname_copilot_short %} can help you quickly understand the purpose of a file, for example, by providing a summary of the file’s contents. You can also ask {% data variables.product.prodname_copilot_short %} to explain specific lines of code within a file. + +{% data reusables.copilot.chat-about-specific-lines %} + +## Next steps + +Now that you know how to use {% data variables.product.prodname_copilot_short %} to explore projects, you can use it to help you understand any repository, file, or line of code on {% data variables.product.prodname_dotcom %}. diff --git a/content/get-started/using-github/communicating-on-github.md b/content/get-started/using-github/communicating-on-github.md index ac26e9d4e5ba..c544d300e650 100644 --- a/content/get-started/using-github/communicating-on-github.md +++ b/content/get-started/using-github/communicating-on-github.md @@ -59,11 +59,11 @@ You can create and participate in issues, pull requests and team discussions, de ### Team discussions -* can be started on your team's page for conversations that span across projects and don't belong in a specific issue or pull request. Instead of opening an issue in a repository to discuss an idea, you can include the entire team by having a conversation in a team discussion. -* allow you to hold discussions with your team about planning, analysis, design, user research and general project decision making in one place.{% ifversion ghes %} -* provide a collaborative experience outside the codebase, allowing the brainstorming of ideas. -* often don’t have a clear owner. -* often do not result in an actionable task.{% endif %} +* Can be started on your team's page for conversations that span across projects and don't belong in a specific issue or pull request. Instead of opening an issue in a repository to discuss an idea, you can include the entire team by having a conversation in a team discussion. +* Allow you to hold discussions with your team about planning, analysis, design, user research and general project decision making in one place.{% ifversion ghes %} +* Provide a collaborative experience outside the codebase, allowing the brainstorming of ideas. +* Often don’t have a clear owner. +* Often do not result in an actionable task.{% endif %} {% endif %} ## Which discussion tool should I use? @@ -148,6 +148,34 @@ The `octocat` team member posted a team discussion, informing the team of variou * Material about the April All Hands is now available for all team members to view. {% endif %} +{% ifversion copilot %} + +## Using {% data variables.product.prodname_copilot_short %} to gain context + +> [!NOTE] {% data reusables.copilot.copilot-requires-subscription %} + +If you need more context or clarity on a specific issue or discussion, you can use {% data variables.product.prodname_copilot %} to help answer your questions. This enables you to quickly gain insights, understand complex threads, and stay aligned with the project’s goals, fostering collaboration and knowledge sharing within the community. + +To ask a question about an issue or discussion: + +1. From anywhere on {% data variables.product.github %}, click the **{% octicon "copilot" aria-hidden="true" %}** {% data variables.product.prodname_copilot %} icon next to the search bar in the top right of the page. + + ![Screenshot of the new conversation button, highlighted with a dark orange outline.](/assets/images/help/copilot/copilot-icon-top-right.png) + +1. In the "Ask {% data variables.product.prodname_copilot_short %}" box, type a question and include the relevant URL in your message. For example, you could ask: + + * `Explain https://github.com/monalisa/octokit/issues/1` + * `Summarize https://github.com/monalisa/octokit/discussions/4` + * `Recommend next steps for https://github.com/monalisa/octokit/issues/2` + * `What are the acceptance criteria for ISSUE URL?` + * `What are the main points made by PERSON in DISCUSSION URL?` + + If you chat with {% data variables.product.prodname_copilot %} from a specific issue or discussion, you don't need to include the URL in your question. + +{% data reusables.copilot.stop-response-generation %} + +{% endif %} + ## Next steps These examples showed you how to decide which is the best tool for your conversations on {% data variables.product.product_name %}. But this is only the beginning; there is so much more you can do to tailor these tools to your needs. diff --git a/content/issues/tracking-your-work-with-issues/configuring-issues/planning-and-tracking-work-for-your-team-or-project.md b/content/issues/tracking-your-work-with-issues/configuring-issues/planning-and-tracking-work-for-your-team-or-project.md index 5e504821894f..7b5c09338124 100644 --- a/content/issues/tracking-your-work-with-issues/configuring-issues/planning-and-tracking-work-for-your-team-or-project.md +++ b/content/issues/tracking-your-work-with-issues/configuring-issues/planning-and-tracking-work-for-your-team-or-project.md @@ -94,6 +94,41 @@ Below we have added a task list to our Project Octocat issue, breaking it down i {% endif %} +{% ifversion copilot %} + +## Understanding new issues + +> [!NOTE] {% data reusables.copilot.copilot-requires-subscription %} + +When working on an unfamiliar or complex issue, {% data variables.product.prodname_copilot %} can help you quickly understand the context, history, and key information, so you can get started faster and with more confidence. + +### Reviewing the issue + +1. Navigate to an issue on {% data variables.product.github %}. + +{% data reusables.copilot.open-copilot %} + +1. At the bottom of the {% data variables.product.prodname_copilot_short %} chat panel, in the "Ask {% data variables.product.prodname_copilot_short %}" box, type a question and press Enter. For example, you could enter: + + * `Summarize the main points of this issue` + * `What’s the goal of this issue?` + +{% data variables.product.prodname_copilot_short %}'s summary will help you capture the purpose and scope of the work. + +### Understanding the history and comments + +Issues often contain a history of discussions and decisions that can provide important context. You can use {% data variables.product.prodname_copilot_short %} to summarize these conversations to identify key points, such as proposed solutions or unanswered questions. For example, you might ask {% data variables.product.prodname_copilot_short %} to summarize recent comments or highlight decisions that have already been made. This helps you focus on what’s most relevant and ensures your contributions are aligned with the team’s priorities. + +### Clarifying technical terms + +Issues often mention technical terms, code, or files that might not be immediately clear. You can use {% data variables.product.prodname_copilot_short %} to get explanations or context for these references. For example, you can ask about the purpose of a file or function, or the meaning of a specific term mentioned in the issue. This helps you understand the details without spending extra time searching through documentation or code. + +### Getting suggestions for next steps + +Once you understand the context of an issue, {% data variables.product.prodname_copilot_short %} can help you figure out how to move forward. You can ask for suggestions on how to approach the work, like fixing a bug or implementing a new feature. For example, you might ask, “What’s the best way to resolve this issue?” or “How can I start addressing this problem?” {% data variables.product.prodname_copilot_short %}'s suggestions can provide useful starting points, helping you plan your work more effectively. + +{% endif %} + ## Making decisions as a team You can use issues and discussions to communicate and make decisions as a team on planned improvements or priorities for your project. Issues are useful when you create them for discussion of specific details, such as bug or performance reports, planning for the next quarter, or design for a new initiative. Discussions are useful for open-ended brainstorming or feedback, outside the codebase and across repositories. For more information, see "[AUTOTITLE](/get-started/using-github/communicating-on-github#which-discussion-tool-should-i-use)." diff --git a/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md index 6f7105920c02..78b27aef69de 100644 --- a/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md +++ b/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md @@ -56,7 +56,7 @@ Before you submit your review, your line comments are _pending_ and only visible You can use [{% data variables.product.prodname_github_codespaces %}](/codespaces/overview) to test, run, and review pull requests. 1. Open the pull request in a codespace, as described in "[AUTOTITLE](/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests#opening-a-pull-request-in-codespaces)." -1. In the Activity Bar, click the **GitHub Pull Request** view. This view only appears when you open a pull request in a codespace. +1. In the Activity Bar, click the **{% data variables.product.github %} Pull Request** view. This view only appears when you open a pull request in a codespace. ![Screenshot of the {% data variables.product.prodname_vscode_shortname %} Activity Bar. The mouse pointer is hovering over an icon displaying the tooltip "{% data variables.product.prodname_dotcom %} Pull Request."](/assets/images/help/codespaces/github-pr-view.png) @@ -79,6 +79,33 @@ For more information on reviewing pull requests in {% data variables.product.pro {% endcodespaces %} {% endif %} +{% webui %} +{% ifversion copilot %} + +## Understanding changes in a pull request + +> [!NOTE] {% data reusables.copilot.copilot-requires-subscription %} + +{% data variables.product.prodname_copilot %} can help you quickly understand the changes in a pull request by providing context and explanations for specific commits. If you’re unsure about the purpose of a particular change or need more details about how it fits into the broader codebase, you can ask {% data variables.product.prodname_copilot_short %} questions about individual commits. + +1. Navigate to a commit on {% data variables.product.github %}. + +{% data reusables.copilot.open-copilot %} + +1. At the bottom of the {% data variables.product.prodname_copilot_short %} chat panel, in the "Ask {% data variables.product.prodname_copilot_short %}" box, type a question and press Enter. For example, you could enter: + + * `Summarize the changes in this commit` + * `Who committed these changes?` + * `When was this commit made?` + + > [!TIP] + > If you know the SHA for a commit, instead of navigating to the commit, you can ask {% data variables.product.prodname_copilot_short %} about the commit from any page in the repository on {% data variables.product.github %} by including the SHA in your message. For example, `What changed in commit a778e0eab?` + +{% data reusables.copilot.stop-response-generation %} + +{% endif %} +{% endwebui %} + ## Reviewing dependency changes If the pull request contains changes to dependencies you can use the dependency review for a manifest or lock file to see what has changed and check whether the changes introduce security vulnerabilities. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)." diff --git a/content/repositories/working-with-files/using-files/index.md b/content/repositories/working-with-files/using-files/index.md index 25a13d198a9b..0d1726ad2cbe 100644 --- a/content/repositories/working-with-files/using-files/index.md +++ b/content/repositories/working-with-files/using-files/index.md @@ -7,9 +7,8 @@ versions: ghec: '*' children: - /navigating-code-on-github - - /viewing-a-file + - /viewing-and-understanding-files - /getting-permanent-links-to-files - /downloading-source-code-archives - /working-with-non-code-files --- - diff --git a/content/repositories/working-with-files/using-files/viewing-a-file.md b/content/repositories/working-with-files/using-files/viewing-and-understanding-files.md similarity index 85% rename from content/repositories/working-with-files/using-files/viewing-a-file.md rename to content/repositories/working-with-files/using-files/viewing-and-understanding-files.md index d3444096d2ac..0d979f409e4f 100644 --- a/content/repositories/working-with-files/using-files/viewing-a-file.md +++ b/content/repositories/working-with-files/using-files/viewing-and-understanding-files.md @@ -1,6 +1,6 @@ --- -title: Viewing a file -intro: You can view raw file content or trace changes to lines in a file and discover how parts of the file evolved over time. +title: Viewing and understanding files +intro: Explore file content and trace changes over time to understand a new codebase and its evolution. redirect_from: - /articles/using-git-blame-to-trace-changes-in-a-file - /articles/tracing-changes-in-a-file @@ -8,14 +8,18 @@ redirect_from: - /github/managing-files-in-a-repository/tracking-changes-in-a-file - /github/managing-files-in-a-repository/managing-files-on-github/tracking-changes-in-a-file - /repositories/working-with-files/using-files/tracking-changes-in-a-file + - /repositories/working-with-files/using-files/viewing-a-file versions: fpt: '*' ghes: '*' ghec: '*' topics: - Repositories -shortTitle: View files and track file changes +shortTitle: View and understand files --- + +{% data variables.product.github %} provides tools to view raw content, trace changes to specific lines, and explore how a file’s content has evolved over time. These insights reveal how code was developed, its current purpose, and its structure, helping you contribute effectively. + ## Viewing or copying the raw file content With the raw view, you can view or copy the raw content of a file without any styling. @@ -100,3 +104,15 @@ git config blame.ignoreRevsFile .git-blame-ignore-revs ## Bypassing `.git-blame-ignore-revs` in the blame view If the blame view for a file shows **Ignoring revisions in .git-blame-ignore-revs**, you can still bypass `.git-blame-ignore-revs` and see the normal blame view. In the URL, append a `~` to the SHA and the **Ignoring revisions in .git-blame-ignore-revs** banner will disappear. + +{% ifversion copilot %} + +## Understanding files with {% data variables.product.prodname_copilot_short %} + +> [!NOTE] {% data reusables.copilot.copilot-requires-subscription %} + +You can also use {% data variables.product.prodname_copilot_short %} to ask about specific lines of code in a file, helping you understand how the code works and reducing the risk of introducing new problems. + +{% data reusables.copilot.chat-about-specific-lines %} + +{% endif %} diff --git a/content/search-github/github-code-search/using-github-code-search.md b/content/search-github/github-code-search/using-github-code-search.md index 8fb796838f01..2a635b716908 100644 --- a/content/search-github/github-code-search/using-github-code-search.md +++ b/content/search-github/github-code-search/using-github-code-search.md @@ -37,6 +37,34 @@ For more information about the search syntax of code search, see "[AUTOTITLE](/s 1. After typing your query, you can also press Enter to go to the full search results view, where you can see each match and a visual interface for applying filters. For more information, see "[Using the search results view](#using-the-search-results-view)." +{% ifversion copilot %} + +## Getting answers with {% data variables.product.prodname_copilot_short %} from the search bar + +> [!NOTE] {% data reusables.copilot.copilot-requires-subscription %} + +You can use {% data variables.product.prodname_copilot %} to ask questions about an entire repository directly from the main search box. Simply type your question into the search bar, and {% data variables.product.prodname_copilot_short %} can provide insights or explanations about the repository’s structure, purpose, or specific components. This makes it easy to get quick answers without navigating through multiple files, helping you stay focused and maintain your workflow. + +1. Navigate to a repository on {% data variables.product.github %}. +1. Press /, or click in the main search box at the top of the page. +1. In the search box, after `repo:OWNER/REPO`, type the question you want to ask {% data variables.product.prodname_copilot_short %}. + + For example, you could enter: + + * `What does this repo do?` + * `Where is authentication implemented in this codebase?` + * `How does license file detection work in this repo?` + +1. Click **Ask {% data variables.product.prodname_copilot_short %}**. + + ![Screenshot of the main search box on {% data variables.product.prodname_dotcom %}. The drop-down option "Ask {% data variables.product.prodname_copilot_short %}" is highlighted with an orange outline.](/assets/images/help/copilot/ask-copilot-from-search-bar.png) + + The {% data variables.product.prodname_copilot_chat %} panel is displayed and {% data variables.product.prodname_copilot_short %} responds to your request. + +{% data reusables.copilot.stop-response-generation %} + +{% endif %} + ## Creating and managing saved searches 1. In the top navigation of {% data variables.product.prodname_dotcom %}, click the search bar and type `saved:`. diff --git a/data/reusables/copilot/chat-about-specific-lines.md b/data/reusables/copilot/chat-about-specific-lines.md new file mode 100644 index 000000000000..56e0e5d16bad --- /dev/null +++ b/data/reusables/copilot/chat-about-specific-lines.md @@ -0,0 +1,31 @@ +1. On {% data variables.product.github %}, navigate to a repository and open a file. +1. Do one of the following: + * To ask a question about the **entire file**, click the {% data variables.product.prodname_copilot_short %} icon ({% octicon "copilot" aria-hidden="true" %}) at the top right of the file view. + + ![Screenshot of the {% data variables.product.prodname_copilot_short %} button, highlighted with a dark orange outline, at the top of the file view.](/assets/images/help/copilot/copilot-button-for-file.png) + + * To ask a question about **specific lines** within the file: + + 1. Click the line number for the first line you want to ask about, hold down Shift, then click the line number for the last line you want to select. + 1. To ask your own question about the selected lines, click the {% data variables.product.prodname_copilot_short %} icon ({% octicon "copilot" aria-hidden="true" %}) to the right of your selection, then type your question in the {% data variables.product.prodname_copilot_chat %} panel. + 1. To ask a predefined question, click the drop-down menu beside the {% data variables.product.prodname_copilot_short %} icon, then choose one of the options. + + ![Screenshot of the {% data variables.product.prodname_copilot_short %} buttons, highlighted with a dark orange outline, to the right of some selected code.](/assets/images/help/copilot/copilot-buttons-inline-code.png) + +1. If you clicked the {% data variables.product.prodname_copilot_short %} icon, type a question in the "Ask {% data variables.product.prodname_copilot_short %}" box at the bottom of the chat panel and press Enter. + + For example, if you are asking about the entire file, you could enter: + * `Explain this file.` + * `How could I improve this code?` + * `How can I test this script?` + + If you are asking about specific lines, you could enter: + * `Explain the function at the selected lines.` + * `How could I improve this class?` + * `Add error handling to this code.` + * `Write a unit test for this method.` + + {% data variables.product.prodname_copilot_short %} responds to your request in the panel. + +{% data reusables.copilot.stop-response-generation %} +1. You can continue the conversation by asking a follow-up question. For example, you could type "tell me more" to get {% data variables.product.prodname_copilot_short %} to expand on its last comment. diff --git a/data/reusables/copilot/copilot-requires-subscription.md b/data/reusables/copilot/copilot-requires-subscription.md new file mode 100644 index 000000000000..45d899e05d41 --- /dev/null +++ b/data/reusables/copilot/copilot-requires-subscription.md @@ -0,0 +1 @@ +You'll need a {% data variables.product.prodname_copilot %} subscription. For more information, see "[AUTOTITLE](/copilot/about-github-copilot/what-is-github-copilot#getting-access-to-copilot)."