Repo sync

content/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.md

@@ -32,6 +32,6 @@ If you do not meet the previous criteria, you can either:
 
 ## Accessing {% data variables.product.prodname_copilot_pro_short %} for free
 
-1. In the upper-right corner of any page, click your profile photo, then click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} Your {% data variables.product.prodname_copilot_short %}**.
+{% data reusables.copilot.your-copilot %}
 1. If you qualify for free access to {% data variables.product.prodname_copilot_short %}, you will see a page titled "{% data variables.product.prodname_copilot_pro %}" informing you that you are eligible. Click **Get access to {% data variables.product.prodname_copilot %}**.
 1. On the page that appears, configure the {% data variables.product.prodname_copilot_short %} use policies to meet your needs, then click **Save and complete**.

content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/managing-your-copilot-plan/disabling-github-copilot-free.md

@@ -17,7 +17,7 @@ redirect_from:
 
 You can disable {% data variables.product.prodname_copilot_free_short %} in your {% data variables.product.github %} account settings. This will disable all features of {% data variables.product.prodname_copilot_short %} on {% data variables.product.github %}.
 
-1. In the upper-right corner of any page, click your profile photo, then click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} Your {% data variables.product.prodname_copilot_short %}**.
+{% data reusables.copilot.your-copilot %}
 1. Under "Visibility," to the right of "Show {% data variables.product.prodname_copilot_short %}, select **Disabled** from the dropdown.
 
 ## Disabling {% data variables.product.prodname_copilot_free_short %} in your IDE

content/copilot/using-github-copilot/code-review/configuring-automatic-code-review-by-copilot.md

@@ -1,7 +1,7 @@
 ---
 title: Configuring automatic code review by Copilot
 shortTitle: Automatic code review
-intro: "Learn how to configure {% data variables.product.prodname_copilot_short %} to automatically review pull requests in a repository."
+intro: "Learn how to configure {% data variables.product.prodname_copilot_short %} to automatically review pull requests."
 versions:
   feature: copilot
 topics:
@@ -10,7 +10,11 @@ topics:
 
 ## About automatic code review
 
-By default, {% data variables.product.prodname_copilot_short %} will only review a pull request if it's assigned to the pull request in the same way you would assign a human reviewer. However, repository owners can configure {% data variables.product.prodname_copilot_short %} to automatically review all pull requests in the repository that are created by people with access to {% data variables.product.prodname_copilot_short %}. Organization owners can configure {% data variables.product.prodname_copilot_short %} to automatically review all pull requests in some or all of the repositories in the organization where the pull request is created by a {% data variables.product.prodname_copilot_short %} user.
+By default, {% data variables.product.prodname_copilot_short %} will only review a pull request if it's assigned to the pull request in the same way you would assign a human reviewer. However:
+
+* Individual users on the {% data variables.product.prodname_copilot_pro_short %} or {% data variables.product.prodname_copilot_pro_plus_short %} plan can configure {% data variables.product.prodname_copilot_short %} to automatically review all pull requests they create.
+* Repository owners can configure {% data variables.product.prodname_copilot_short %} to automatically review all pull requests in the repository that are created by people with access to {% data variables.product.prodname_copilot_short %}.
+* Organization owners can configure {% data variables.product.prodname_copilot_short %} to automatically review all pull requests in some or all of the repositories in the organization where the pull request is created by a {% data variables.product.prodname_copilot_short %} user.
 
 ### Triggering an automatic pull request review
 
@@ -29,6 +33,18 @@ After you configure automatic code review, {% data variables.product.prodname_co
 
 {% data variables.copilot.copilot_code-review_short %} is a premium feature with a per-person monthly quota. When {% data variables.product.prodname_copilot_short %} carries out an automatic review, it uses one premium request from the quota of the user who created the pull request. For more information, see [AUTOTITLE](/copilot/using-github-copilot/code-review/using-copilot-code-review#code-review-monthly-quota).
 
+## Configuring automatic code review for all pull requests you create
+
+> [!NOTE]
+> This is only available if you are on the {% data variables.product.prodname_copilot_pro_short %} or {% data variables.product.prodname_copilot_pro_plus_short %} plan.
+
+{% data reusables.copilot.your-copilot %}
+1. Locate the **Automatic {% data variables.copilot.copilot_code-review_short %}** option and click the dropdown button.
+
+   ![Screenshot of the "Automatic {% data variables.copilot.copilot_code-review_short %}" setting with the dropdown menu displayed.](/assets/images/help/copilot/code-review/automatic-code-review-personal.png)
+
+1. In the dropdown menu, select **Enabled**.
+
 ## Configuring automatic code review for a single repository
 
 {% data reusables.repositories.navigate-to-repo %}

content/copilot/using-github-copilot/code-review/using-copilot-code-review.md

@@ -87,23 +87,6 @@ When you reach your monthly quota you will not be able to get a code review from
 
 {% data variables.copilot.copilot_code-review_short %} on the {% data variables.product.github %} website supports all languages.
 
-The following languages have general availability support:
-
-* C
-* C#
-* C++
-* Go
-* Java
-* JavaScript
-* Kotlin
-* Markdown
-* Python
-* Ruby
-* Swift
-* TypeScript
-
-All other languages are supported as a {% data variables.release-phases.public_preview %}.
-
 {% endwebui %}
 
 ### Validating {% data variables.product.prodname_copilot_short %} code reviews
@@ -167,7 +150,7 @@ To request a re-review from {% data variables.product.prodname_copilot_short %},
 
 ## Enabling automatic reviews
 
-By default, you manually request a review from {% data variables.product.prodname_copilot_short %} on each pull request, in the same way you would request a review from a human. However, you can set up {% data variables.product.prodname_copilot_short %} to automatically review all pull requests in a repository, or for all repositories in an organization. See [AUTOTITLE](/copilot/using-github-copilot/code-review/configuring-automatic-code-review-by-copilot).
+By default, you manually request a review from {% data variables.product.prodname_copilot_short %} on each pull request, in the same way you would request a review from a human. However, you can set up {% data variables.product.prodname_copilot_short %} to automatically review all pull requests. See [AUTOTITLE](/copilot/using-github-copilot/code-review/configuring-automatic-code-review-by-copilot).
 
 ## Customizing {% data variables.product.prodname_copilot_short %}'s reviews with coding guidelines
 

content/get-started/exploring-projects-on-github/contributing-to-a-project.md

@@ -16,6 +16,12 @@ redirect_from:
   - /get-started/quickstart/contributing-to-projects
 ---
 
+Contributing to a project on {% data variables.product.github %} is an essential skill for developers and collaborators working together to achieve shared goals. Whether you're fixing bugs, adding features, or improving documentation, the process of contributing ensures structured and efficient collaboration.
+
+By following the {% data variables.product.github %} flow of forking repositories, creating branches, and submitting pull requests, you can propose changes to a project and get feedback without disrupting other people's work.
+
+This guide provides instructions on contributing to a project using the GitHub UI and the command line. For more information on contributing with GitHub Desktop, see [AUTOTITLE](/desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop). For the same with GitHub CLI (Command Line Interface), see [AUTOTITLE](/github-cli/github-cli/quickstart).
+
 ## About forking
 
 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.
@@ -50,11 +56,9 @@ You've successfully forked the Spoon-Knife repository, but so far, it only exist
 
 You can clone your fork with the command line, {% data variables.product.prodname_cli %}, or {% data variables.product.prodname_desktop %}.
 
-{% webui %}
-
 1. On {% data variables.product.github %}, navigate to **your fork** of the Spoon-Knife repository.
 {% data reusables.repositories.copy-clone-url %}
-{% data reusables.command_line.open_the_multi_os_terminal %}
+1. On Mac or Linux, open Terminal. On Windows, open Git Bash.
 {% data reusables.command_line.change-current-directory-clone %}
 1. Type `git clone`, and then paste the URL you copied earlier. It will look like this, with your {% data variables.product.github %} username instead of `YOUR-USERNAME`:
 
@@ -73,133 +77,44 @@ You can clone your fork with the command line, {% data variables.product.prodnam
    > Unpacking objects: 100% (10/10), done.
    ```
 
-{% endwebui %}
-
-{% cli %}
-
-{% data reusables.cli.cli-learn-more %}
-
-To create a clone of your fork, use the `--clone` flag.
-
-```shell
-gh repo fork REPOSITORY --clone=true
-```
-
-{% endcli %}
-
-{% desktop %}
-
-{% data reusables.desktop.choose-clone-repository %}
-{% data reusables.desktop.cloning-location-tab %}
-{% data reusables.desktop.cloning-repository-list %}
-{% data reusables.desktop.choose-local-path %}
-{% data reusables.desktop.click-clone %}
-
-{% enddesktop %}
-
 ## 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 {% 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 %}
-
 ```shell
 git branch BRANCH-NAME
 git checkout BRANCH-NAME
 ```
 
-{% endwebui %}
-
-{% cli %}
-
-```shell
-git branch BRANCH-NAME
-git checkout BRANCH-NAME
-```
-
-{% endcli %}
-
-{% desktop %}
-
-For more information about how to create and manage branches in {% data variables.product.prodname_desktop %}, see [AUTOTITLE](/desktop/making-changes-in-a-branch/managing-branches-in-github-desktop).
-
-{% enddesktop %}
-
 ## 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 {% 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.
 
-{% webui %}
-
-```shell
-git add .
-git commit -m "a short description of the change"
-```
-
-{% endwebui %}
-
-{% cli %}
-
 ```shell
 git add .
 git commit -m "a short description of the change"
 ```
 
-{% endcli %}
-
-{% desktop %}
-
-For more information about how to stage and commit changes in {% data variables.product.prodname_desktop %}, see [AUTOTITLE](/desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project-in-github-desktop#selecting-changes-to-include-in-a-commit).
-
-{% enddesktop %}
-
-When you stage and commit files, you essentially tell Git, "Okay, take a snapshot of my changes!" You can continue to make more changes, and take more commit snapshots.
+When you stage and commit files, you essentially tell Git, "Take a snapshot of my changes." You can continue to make more changes and take more commit snapshots.
 
 Right now, your changes only exist locally. When you're ready to push your changes up to {% data variables.product.github %}, push your changes to the remote.
 
-{% webui %}
-
 ```shell
 git push
 ```
 
-{% endwebui %}
-
-{% cli %}
-
-```shell
-git push
-```
-
-{% endcli %}
-
-{% desktop %}
-
-For more information about how to push changes in {% data variables.product.prodname_desktop %}, see [AUTOTITLE](/desktop/making-changes-in-a-branch/pushing-changes-to-github-from-github-desktop).
-
-{% enddesktop %}
-
 ## Making a pull request
 
-At last, you're ready to propose changes into the main project! This is the final step in producing a fork of someone else's project, and arguably the most important. If you've made a change that you feel would benefit the community as a whole, you should definitely consider contributing back.
+Creating a pull request is the final step in producing a fork of someone else's project. When you've made a beneficial change and want to propose it to the original repository, you'll create a pull request for a maintainer to review.
 
-To do so, head on over to the repository on {% data variables.product.github %} where your project lives. For this example, it would be at `https://github.com/<your_username>/Spoon-Knife`. You'll see a banner indicating that your branch is one commit ahead of `octocat:main`. Click **Contribute** and then **Open a pull request**.
+To do so, navigate to the repository on {% data variables.product.github %} where your project lives. For this example, it would be at `https://github.com/<your_username>/Spoon-Knife`. You'll see a banner indicating that your branch is one commit ahead of `octocat:main`. Click **Contribute** and then **Open a pull request**.
 
 {% data variables.product.github %} will bring you to a page that shows the differences between your fork and the `octocat/Spoon-Knife` repository. Click **Create pull request**.
 
 {% data variables.product.github %} will bring you to a page where you can enter a title and a description of your changes. It's important to provide as much useful information and a rationale for why you're making this pull request in the first place. The project owner needs to be able to determine whether your change is as useful to everyone as you think it is. Finally, click **Create pull request**.
 
-## Managing feedback
-
-Pull requests are an area for discussion. Don't be offended if the project owner rejects your pull request, or asks for more information on why it's been made. Even if the project owner chooses not to merge your pull request, your changes still exist in your fork. It could be that someone else will find your fork much more valuable than the original project.
-
-## Finding projects
-
-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

data/reusables/copilot/your-copilot.md

@@ -0,0 +1 @@
+1. In the upper-right corner of any page, click your profile photo, then click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} Your {% data variables.product.prodname_copilot_short %}**.

src/events/components/Survey.tsx

@@ -201,7 +201,7 @@ export const Survey = () => {
             </label>
             <input
               type="email"
-              className="form-control input-sm width-full"
+              className="form-control input-sm width-full color-bg-transparent"
               name="survey-email"
               id="survey-email"
               value={email}