NetSparkleUpdater / NetSparkleUpdater/NetSparkle
CI/CD: Migrate away from nitz/publish-nuget and use dotnet commands
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 832
- Forks
- 103
- PR merge metrics
- No merged PRs in 30d
Description
We should be able to migrate away from nitz/publish-nuget usage and just use these commands:
dotnet restore ...
dotnet build ...
dotnet pack ...
dotnet nuget push ...
This would simplify the CI/CD use a little bit and allow us to make tweaks easier without relying on an external action that is not updated anymore.
I'd like to use variables or something to keep the code clean and just do things in a loop (or otherwise save the hassle of having those repeating lines of commands repeated a bunch of times). Not sure if that's possible off the top of my head in GitHub actions.
Note on WinForms: probably need a dotnet restore too, based on this run's output: https://github.com/NetSparkleUpdater/NetSparkle/actions/runs/12979626914/job/36195840714
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Search the GitHub Actions workflow files for nitz/publish-nuget and review the existing package, build, and WinForms steps. Replace the external action with the listed dotnet commands, keep repeated configuration manageable where practical, include restore for WinForms, and verify the workflows complete successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, github-actions
- Domain
- build-system, ci-cd
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100