GitHub Actions
If approved, @BrandonPotter will need to update the repository settings (fix what's required) and add a repository secret for NuGet.
Also of note: committing and pushing to "master" requires a review from one of us already so I thought it made sense to go ahead and push to NuGet here.
I also realize that this current implementation will attempt to push to NuGet all three times once a pull request is merged. One option is to add OS to the if on that step. The other option is to have a secondary "release" workflow that only pushes to NuGet when running on a tag. I have this scenario on one or two of my own personal repos and I'm happy to duplicate that here.
@flytzen ?
pinged @BrandonPotter to make the admin updates so we can merge.
Thanks for this! Checking on the NG key..
NUGET_KEY added to repository secrets
NUGET_KEYadded to repository secrets
Great. Can you also update the merge requirements so the currently required status isn't? Or if you're okay granting me permissions I can fix that.
This has been in limbo for almost a year. @BrandonPotter any chance of updating the required checks or granting admin privileges on the repo (even just temporarily) so I can take care of that?