It should work in a way (tested locally just by setting environment variables to simulate AppVeyor build) that if we tag a commit where the tag will match the nuget version in release notes then it will push the nuget. The nuget API key secret is stored in an environment variable and according to AppVeyor it should be set if and only if the build is triggered for an internal build (that means from branch from this repository, not in a pull request coming from a different repository). So, after merging (I will use squash merge), I will create tag 2.0.0-rc1 which will be published as nuget.
It should work in a way (tested locally just by setting environment variables to simulate AppVeyor build) that if we tag a commit where the tag will match the nuget version in release notes then it will push the nuget. The nuget API key secret is stored in an environment variable and according to AppVeyor it should be set if and only if the build is triggered for an internal build (that means from branch from this repository, not in a pull request coming from a different repository). So, after merging (I will use squash merge), I will create tag 2.0.0-rc1 which will be published as nuget.