Is there an existing issue for this?
What is the feature you want?
A PR I submitted to winget-pkgs got merged so there is now a SnapXL.SnapX package. It would be great to setup a github action workflow into this repo so new SnapX releases are automatically pushed to winget. Your windows userbase can then simply
winget install SnapXL.SnapX
What does it solve?
The standard way to do it is to use winget-releaser (which uses Komac under the hood). It requires a Classic Github Personal Access Token with public_repo scope is created, following this link, then the Token can be added to the repo as a secret named WINGET_ACC_TOKEN. See below, that user also will have to fork the winget-pkgs repository.
Notes:
You will need to create a classic Personal Access Token (PAT) with public_repo scope. New fine-grained PATs aren't supported by the action.
Fork microsoft/winget-pkgs under the same account/organization as the project's repository. If you are forking winget-pkgs on a different account (e.g. bot/personal account), you can use the fork-user input to specify the username of the account where the fork is present.
Here is the standard action workflow file to do so
name: Publish release to WinGet
on:
release:
types: [released]
jobs:
publish:
runs-on: windows-latest
steps:
- uses: vedantmgoyal9/winget-releaser@latest
with:
identifier: SnapXL.SnapX
installers-regex: '\-X64\.msi'
token: ${{ secrets.WINGET_ACC_TOKEN }}
Code of Conduct
Is there an existing issue for this?
What is the feature you want?
A PR I submitted to winget-pkgs got merged so there is now a
SnapXL.SnapXpackage. It would be great to setup a github action workflow into this repo so new SnapX releases are automatically pushed to winget. Your windows userbase can then simplyWhat does it solve?
The standard way to do it is to use winget-releaser (which uses Komac under the hood). It requires a Classic Github Personal Access Token with public_repo scope is created, following this link, then the Token can be added to the repo as a secret named
WINGET_ACC_TOKEN. See below, that user also will have to fork the winget-pkgs repository.Here is the standard action workflow file to do so
Code of Conduct