Closed asilentdreamer closed 3 months ago
@Byron, sorry to ping you here. 🙏🏼
Are you willing to integrate WinGet Releaser to your GitHub Workflows? It's better the publisher & author takes full control of their manifests in microsoft/winget-pkgs.
Enabling this integration requires the package already available in the repository. I'm currently working on this "very first" manifest version.
Thanks a lot for your help with this!
I'd be happy to integrate it into the GitHub CI, as it's preferable to control what goes into a package if possible. However, I'd definitely appreciate if all I had to do was to setup an account somewhere and add the secret to the project's CI. Maybe that's possible, but I'd need your guidance in any case.
The "very first" manifest of this package is successfully merged :tada:
I can help creating pull request for integrating WinGet Releaser into the release workflow. :heart:
I can help creating pull request for integrating WinGet Releaser into the release workflow. ❤️
Yes, I'd definitely appreciate that.
Seems modifications are valid. Pull request of this issue will be created soon. ❤️
[!IMPORTANT]
According to Configuration Options of WinGet Releaser, repository owner have to configure a repository secret (called
WINGET_TOKEN
in my YAML) forkomac.exe
so it can create PRs via GitHub API.After it's successfully integrated, above configurations is the only needed step for you. ❤️ I can't do further help configuring those for you via PR. 😞
I have opened a request for including dua-cli in winget with the tentative package name
byron.dua-cli
. It would be great if there are any additional inputs there with changes if required.Link to request for inclusion: https://github.com/microsoft/winget-pkgs/issues/167128