-
Notifications
You must be signed in to change notification settings - Fork 101
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
Nuget package #37
Comments
@mpolicki - Hi, absolutely. I personally haven't used dotnet in a while now, so I'm a bit out of date on this, and GitHub didn't have the inbuilt CI back then (I remember I wanted to automate the publishing which never happened). I'd love for someone to contribute a PR on this with something like a Github actions based workflow on git tags for release and / or a continuous |
It's been a while, but I've made some progress on this. I've used the Publish NuGet 2 Github Action on my fork of the repository successfully. What it does is run on every push, and for the specified project (can be multiple in a single job), it checks whether the version in the repository is greater than the version on Nuget. If it is, it builds the project and uploads to Nuget. You can see a run here. So, to have an update published on Nuget, all that would be required is to increment the version in the project file. Would that be an acceptable workflow for you? |
Hi @mpolicki - This is great. Absolutely! I'd love for this to be easier to use! Thank you so much for taking this up and sharing this back. Sorry for the late reply. |
No problem :) The pull request is #50 |
The last nuget package (4.0.0) was published on 8/21/2017 and there have been changes to the code since then. Could we get more frequent package updates so that we don't have to build from source?
I don't know if there exists a solution where users could request that the project be packaged and published automatically, by clicking a link perhaps. If such a solution does exist, perhaps it would be a good idea?
The text was updated successfully, but these errors were encountered: