-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
publish component on NuGet #26
Comments
We use it as a submodule, and you're welcome to do the same.
Alternatively you're welcome to help us create necessary CI/CD pipelines
(testing, publishing, etc) and we'll have it published on NuGet.
…On Sun, 23 May 2021 at 11:27, Érico Vieira Porto ***@***.***> wrote:
This is a great component that is build with pure C#! any chance of
getting it available on NuGet, so it can be pulled by other projects?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#26>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABBTEXTX65T4QCYVCHBA74LTPBKYNANCNFSM45LFZKDQ>
.
|
Would you willing to have a Azure classic pipeline? A current Azure/GitHub Actions I think can only go as far as building/testing NuGet package, but publishing requires someone with a valid NuGet account, and I think to be a valid person it would be done manually, which I think only Azure Classic supports - it will be a pipeline with a button and one person will have to manually click this button for the package to be uploaded. I used it here: https://github.com/ericoporto/xiph-for-ags |
We have a NuGet account. @mast-eu how are we publishing to NuGet? |
At the moment I'm still doing manual uploads. Improvements would be highly appreciated. |
This is a great component that is build with pure C#! any chance of getting it available on NuGet, so it can be pulled by other projects?
The text was updated successfully, but these errors were encountered: