From d1bd744c0e28a884db0c48e15f2b8fa9191a1720 Mon Sep 17 00:00:00 2001 From: Thomas Weichhart <63959563+ThomasW2005@users.noreply.github.com> Date: Fri, 5 Dec 2025 09:04:01 +0100 Subject: [PATCH 1/2] Update Oh-My-Posh workflow link in README Source: https://github.com/JanDeDobbeleer/oh-my-posh/issues/7018#issuecomment-3612451136 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 19dd4cb6..286bd2ea 100644 --- a/README.md +++ b/README.md @@ -64,7 +64,7 @@ Click on the individual commands to learn more. You can use WingetCreate to update your existing app manifest as part of your CI/CD pipeline. For reference, see the final task in this repo's [release Azure pipeline](https://github.com/microsoft/winget-create/blob/main/pipelines/azure-pipelines.release.yml). If you are utilizing GitHub Actions as your CI pipeline, you can refer to the following repositories that have implemented WingetCreate within their release pipelines: - [DevHome](https://github.com/microsoft/devhome/blob/main/.github/workflows/winget-submission.yml) -- [Oh-My-Posh](https://github.com/JanDeDobbeleer/oh-my-posh/blob/main/.github/workflows/winget.yml) +- [Oh-My-Posh](https://github.com/JanDeDobbeleer/oh-my-posh/blob/main/.github/workflows/release.yml#L139) - [PowerToys](https://github.com/microsoft/PowerToys/blob/main/.github/workflows/package-submissions.yml) - [Terminal](https://github.com/microsoft/terminal/blob/main/.github/workflows/winget.yml) From b8d155c914bb05b20c770e0a9f9e2afa042601d3 Mon Sep 17 00:00:00 2001 From: Thomas Weichhart <63959563+ThomasW2005@users.noreply.github.com> Date: Tue, 6 Jan 2026 10:01:51 +0100 Subject: [PATCH 2/2] Add links to additional CI/CD examples in README --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 286bd2ea..aee2f09e 100644 --- a/README.md +++ b/README.md @@ -63,10 +63,12 @@ Click on the individual commands to learn more. You can use WingetCreate to update your existing app manifest as part of your CI/CD pipeline. For reference, see the final task in this repo's [release Azure pipeline](https://github.com/microsoft/winget-create/blob/main/pipelines/azure-pipelines.release.yml). If you are utilizing GitHub Actions as your CI pipeline, you can refer to the following repositories that have implemented WingetCreate within their release pipelines: -- [DevHome](https://github.com/microsoft/devhome/blob/main/.github/workflows/winget-submission.yml) +- [Copilot CLI](https://github.com/github/copilot-cli/blob/v0.0.368-2/.github/workflows/winget.yml) +- [Edit](https://github.com/microsoft/edit/blob/main/.github/workflows/winget.yml) - [Oh-My-Posh](https://github.com/JanDeDobbeleer/oh-my-posh/blob/main/.github/workflows/release.yml#L139) - [PowerToys](https://github.com/microsoft/PowerToys/blob/main/.github/workflows/package-submissions.yml) - [Terminal](https://github.com/microsoft/terminal/blob/main/.github/workflows/winget.yml) +- [WinGet Studio](https://github.com/microsoft/winget-studio/blob/main/.github/workflows/winget.yml) You can also check out this [episode of Open at Microsoft](https://learn.microsoft.com/en-us/shows/open-at-microsoft/wingetcreate-keeping-winget-packages-up-to-date) where we cover the same topic.