while nightly builds are useful they also cause
a large amount of spam on the main project
nuget. here we try to change the package id
so that it will be hosted as a separate package
while having all the same code and namespaces
this means people can opt into the nightly builds
while keeping the version history of the released
package tidy.
no idea if this will work because actions and
yaml is my idea of hell and is impossible to
debug, but let's give it a go
probably safer to move the dependent job into the
same action file. of course there's probably a way to
separate them but there's also no way to test for certain
i think you need to use the double brackets and scope
to the action secrets to access the api key. who knows
it's not like there's any validation or debugging or testing
capability because the entire field of devops has soup for
brain 🧌
this is intended to create nightly build with package
versions of the form x.y.z-yyyyMMdd.sha and
push them to nuget automatically, only where there
are new changes per day. since devops is a nightmare
and entirely untestable we will have to go through 20
iterations to actually get this to work
