Skip to content

Commit fd684f3

Browse files
authored
Merge pull request #39119 from github/repo-sync
Repo sync
2 parents 3bf9fc7 + dc72c6b commit fd684f3

File tree

100 files changed

+3440
-1528
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

100 files changed

+3440
-1528
lines changed

CHANGELOG.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,12 @@ Get started at [Achieving your company's engineering goals with GitHub Copilot](
1212

1313
**27 June 2025**
1414

15+
We've published a new guide about how to combine use of GitHub Copilot's agent mode with Model Context Protocol (MCP) servers to complete complex tasks through agentic "loops" - illustrated through an accessibility compliance example. The guide also discusses best practices and benefits around using these two features together. See [Enhancing Copilot agent mode with MCP](https://docs.github.com/copilot/tutorials/enhancing-copilot-agent-mode-with-mcp).
16+
17+
<hr>
18+
19+
**27 June 2025**
20+
1521
We’ve published a new set of new documentation articles designed to help users make the most of the **Dependabot metrics page** in the organization’s security overview.
1622

1723
These clear, actionable guides help users:
Binary file not shown.

content/actions/how-tos/managing-workflow-runs-and-deployments/managing-workflow-runs/manually-running-a-workflow.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,7 @@ redirect_from:
1010
- /actions/managing-workflow-runs/manually-running-a-workflow
1111
- /actions/using-workflows/manually-running-a-workflow
1212
- /actions/managing-workflow-runs-and-deployments/managing-workflow-runs/manually-running-a-workflow
13+
- /articles/configuring-a-workflow
1314
---
1415

1516
{% data reusables.actions.enterprise-github-hosted-runners %}

content/admin/configuring-settings/configuring-network-settings/configuring-built-in-firewall-rules.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ shortTitle: Configure firewall rules
1919
---
2020
## About {% data variables.location.product_location %}'s firewall
2121

22-
{% data variables.product.prodname_ghe_server %} uses Ubuntu's Uncomplicated Firewall (UFW) on the virtual appliance. For more information see [UFW](https://help.ubuntu.com/community/UFW) in the Ubuntu documentation. {% data variables.product.prodname_ghe_server %} automatically updates the firewall allowlist of allowed services with each release.
22+
{% data variables.product.prodname_ghe_server %} uses Ubuntu's Uncomplicated Firewall (UFW) on the virtual appliance. For more information see [Firewall](https://documentation.ubuntu.com/server/how-to/security/firewalls/#ufw-uncomplicated-firewall) in the Ubuntu documentation. {% data variables.product.prodname_ghe_server %} automatically updates the firewall allowlist of allowed services with each release.
2323

2424
After you install {% data variables.product.prodname_ghe_server %}, all required network ports are automatically opened to accept connections. Every non-required port is automatically configured as `deny`, and the default outgoing policy is configured as `allow`. Stateful tracking is enabled for any new connections; these are typically network packets with the `SYN` bit set. For more information, see [AUTOTITLE](/admin/configuration/configuring-network-settings/network-ports).
2525

content/admin/enforcing-policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -44,13 +44,13 @@ You can use a Linux container management tool to build a pre-receive hook enviro
4444
```shell
4545
$ docker build -f Dockerfile.debian -t pre-receive.debian .
4646
> [+] Building 0.6s (6/6) FINISHED docker:desktop-linux
47-
> => [internal] load build definition from Dockerfile.debian
48-
> => [1/2] FROM docker.io/library/debian:latest@sha256:80dd3c3b9c6cecb9f1667e9290b3bc61b78c2678c02cbdae5f0fea92cc6
49-
> => [2/2] RUN apt-get update && apt-get install -y git bash curl
50-
> => exporting to image
51-
> => => exporting layers
52-
> => => writing image sha256:b57af4e24082f3a30a34c0fe652a336444a3608f76833f5c5fdaf4d81d20c3cc
53-
> => => naming to docker.io/library/pre-receive.debian
47+
> => [internal] load build definition from Dockerfile.debian
48+
> => [1/2] FROM docker.io/library/debian:latest@sha256:80dd3c3b9c6cecb9f1667e9290b3bc61b78c2678c02cbdae5f0fea92cc6
49+
> => [2/2] RUN apt-get update && apt-get install -y git bash curl
50+
> => exporting to image
51+
> => => exporting layers
52+
> => => writing image sha256:b57af4e24082f3a30a34c0fe652a336444a3608f76833f5c5fdaf4d81d20c3cc
53+
> => => naming to docker.io/library/pre-receive.debian
5454
```
5555

5656
1. Create a container:
@@ -82,7 +82,7 @@ You can use a Linux container management tool to build a pre-receive hook enviro
8282
> * `/bin/sh` must exist and be executable, as the entry point into the chroot environment.
8383
> * Unlike traditional chroots, the `dev` directory is not required by the chroot environment for pre-receive hooks.
8484
85-
For more information about creating a chroot environment see [Chroot](https://wiki.debian.org/chroot) from the _Debian Wiki_ or [BasicChroot](https://help.ubuntu.com/community/BasicChroot) from the _Ubuntu Community Help Wiki_.
85+
For more information about creating a chroot environment, see [Chroot](https://wiki.debian.org/chroot) from the Debian Wiki.
8686

8787
## Uploading a pre-receive hook environment on {% data variables.product.prodname_ghe_server %}
8888

content/admin/managing-iam/provisioning-user-accounts-with-scim/configuring-authentication-and-provisioning-with-pingfederate.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ In addition:
5454
* You may need to configure the firewall in PingFederate to allow outbound connections to {% ifversion ghes %}the `https://HOSTNAME/api/v3/scim/v2` endpoint on your {% data variables.product.prodname_ghe_server %} instance.{% else %}the SCIM endpoints on {% data variables.product.github %}:
5555
* For **{% data variables.product.prodname_dotcom_the_website %}**: `https://api.github.com/scim/v2/enterprises/ENTERPRISE`
5656
* For **{% data variables.enterprise.data_residency_site %}**: `https://api.SUBDOMAIN.ghe.com/scim/v2/enterprises/SUBDOMAIN`{% endif %}
57-
* PingFederate's "provisioner mode" must be set to a value that allows SCIM provisioning. See the "Before you begin" section in PingIdentity's [Configuring outbound provisioning settings](https://docs.pingidentity.com/pingfederate/11.2/administrators_reference_guide/help_protocolsettingstasklet_saasglobalprovisioningsettingsstate.html) guide.
57+
* PingFederate's "provisioner mode" must be set to a value that allows SCIM provisioning. See the "Before you begin" section in PingIdentity's [Configuring outbound provisioning settings](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/help_protocolsettingstasklet_saasglobalprovisioningsettingsstate.html) guide.
5858
* During this procedure, you will need to upload an X509 certificate to PingFederate. You may want to create and store the certificate before proceeding. You will also need the challenge password for the certificate. See the [Example of creating an X509 certificate](#example-of-creating-an-x509-certificate) section later in this article.
5959
{%- ifversion ghec %}
6060
* During this procedure, you will need to upload a SAML metadata file to PingFederate. If you're setting up an enterprise that uses **{% data variables.enterprise.data_residency_short %} on {% data variables.enterprise.data_residency_site %}**, it is easiest to create this file before you start. See [Creating a SAML metadata file for {% data variables.enterprise.data_residency_site %}](#creating-a-saml-metadata-file-for-ghecom).

content/admin/managing-iam/reconfiguring-iam-for-enterprise-managed-users/migrating-your-enterprise-to-a-new-identity-provider-or-tenant.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ If you don't already have single sign-on recovery codes for your enterprise, dow
7272
1. On your current IdP, deactivate provisioning in the application for {% data variables.product.prodname_emus %}.
7373
* If you use Entra ID, navigate to the "Provisioning" tab of the application, and then click **Stop provisioning**.
7474
* If you use Okta, navigate to the "Provisioning" tab of the application, click the **Integration** tab, and then click **Edit**. Deselect **Enable API integration**.
75-
* If you use PingFederate, navigate to the channel settings in the application. From the **Activation & Summary** tab, click **Active** or **Inactive** to toggle the provisioning status, and then click **Save**. For more information about managing provisioning, see [Reviewing channel settings](https://docs.pingidentity.com/pingfederate/11.2/administrators_reference_guide/help_saaschanneltasklet_saasactivationstate.html) and [Managing channels](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/help_saasmanagementtasklet_saasmanagementstate.html) in the PingFederate documentation.
75+
* If you use PingFederate, navigate to the channel settings in the application. From the **Activation & Summary** tab, click **Active** or **Inactive** to toggle the provisioning status, and then click **Save**. For more information about managing provisioning, see [Reviewing channel settings](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/help_saaschanneltasklet_saasactivationstate.html) and [Managing channels](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/help_saasmanagementtasklet_saasmanagementstate.html) in the PingFederate documentation.
7676
* If you use another identity management system, consult the system's documentation, support team, or other resources.
7777

7878
### 4. Disable authentication for your enterprise

content/copilot/tutorials/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ children:
1818
- /learning-a-new-programming-language-with-github-copilot
1919
- /modernizing-legacy-code-with-github-copilot
2020
- /using-copilot-to-migrate-a-project
21-
- /upgrading-java-projects-with-github-copilot
21+
- /upgrading-projects-with-github-copilot
2222
- /rolling-out-github-copilot-at-scale
2323
redirect_from:
2424
- /copilot/using-github-copilot/guides-on-using-github-copilot

content/copilot/tutorials/upgrading-java-projects-with-github-copilot.md

Lines changed: 0 additions & 106 deletions
This file was deleted.
Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
---
2+
title: Upgrading projects with GitHub Copilot
3+
shortTitle: Upgrade projects
4+
intro: 'You can use {% data variables.product.prodname_copilot %} to upgrade your Maven and Gradle Java applications and .NET applications.'
5+
versions:
6+
feature: copilot
7+
topics:
8+
- Copilot
9+
redirect_from:
10+
- /copilot/using-github-copilot/guides-on-using-github-copilot/upgrading-java-projects-with-github-copilot
11+
- /copilot/tutorials/upgrading-java-projects-with-github-copilot
12+
---
13+
14+
> [!NOTE]
15+
> "GitHub Copilot app modernization – upgrade for Java" and "GitHub Copilot app modernization – Upgrade for .NET" are currently in {% data variables.release-phases.public_preview %} and subject to change.
16+
17+
## Introduction
18+
19+
{% data variables.product.prodname_copilot %} can help streamline the process of modernizing and upgrading your Java and .NET applications. {% data variables.product.prodname_copilot_short %} will analyze the project, generate a plan, automatically fix issues it encounters when carrying out the plan, and produce a summary.
20+
21+
## Upgrading Java projects
22+
23+
You can upgrade a Git-based Maven or Gradle Java project using {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode %}. You will need:
24+
25+
* Either a **{% data variables.copilot.copilot_for_business %}** or **{% data variables.copilot.copilot_enterprise %}** [subscription plan](/copilot/about-github-copilot/subscription-plans-for-github-copilot).
26+
* The latest version of [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/).
27+
* For Maven-based projects, access to the public Maven Central repository.
28+
* Installed versions of both the source and target JDKs.
29+
30+
For the next steps, see [Quickstart: upgrade a Java project with GitHub Copilot App Modernization - upgrade for Java (preview)](https://learn.microsoft.com/en-gb/java/upgrade/quickstart-upgrade) on Microsoft Learn.
31+
32+
## Upgrading .NET projects
33+
34+
You can also upgrade a .NET project using {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vs %}. You will need:
35+
36+
* Either a **{% data variables.copilot.copilot_pro %}**, **{% data variables.copilot.copilot_pro_plus %}**, **{% data variables.copilot.copilot_for_business %}** or **{% data variables.copilot.copilot_enterprise %}** [subscription plan](/copilot/about-github-copilot/subscription-plans-for-github-copilot).
37+
* The latest release of {% data variables.product.prodname_vs %} Enterprise, Professional or Community 2022.
38+
39+
For the next steps, see [GitHub Copilot app modernization - upgrade for .NET](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.GitHubCopilotUpgradeAgent) on Microsoft Visual Studio Marketplace.

0 commit comments

Comments
 (0)