---
title: Update-ForgePackageConfig.ps1
description: The Forge package-config tool now ships as automation inside the azure-devops Agent Skill.
---

# Update-ForgePackageConfig.ps1

!!! info "This tool moved into the azure-devops skill"
    `Update-ForgePackageConfig.ps1` is now part of the **azure-devops** Agent Skill and is
    invoked through it rather than maintained as a standalone contributor script. It lives in
    the repository at `.github/skills/azure-devops/scripts/Update-ForgePackageConfig.ps1`, and
    its parameters, workflow, and troubleshooting are documented in that skill's `SKILL.md` and
    `references/update-script.md`.

    See [GitHub Copilot Configuration](./copilot-skills.md) for how Forge skills are structured
    and invoked.

## What it does

It keeps the .NET package block in `.azdo/templates/forge-orchestrator.yml` in sync with the
`src/dotnet` project layout — regenerating each package's `sourceRoot`, `packagePath`, and
`dependsOn` so pipeline orchestration builds, packs, tests, and publishes the right projects in
the right dependency order. Run it after adding, renaming, or moving a .NET project, or when
intra-repo project references change.

## How to run it

This is platform automation surfaced through the **azure-devops** skill — ask Copilot to update
the Forge package configuration, or run it directly from the repository root:

```powershell
./.github/skills/azure-devops/scripts/Update-ForgePackageConfig.ps1 -WhatIf
```

`-WhatIf` previews the regenerated package entries without writing the YAML. For the full
parameter set and workflow, see the skill reference linked above.