GitHubCI: no need to filter by branch

[knocte]

Removing the branch filters from the GitHub workflows allows potential contributors to see the CI status of their contributions before they propose a PR (therefore allowing them to improve their work before putting it up for review).

[juanfranblanco]

@knocte Hola!!, this is going to need a different nuget build (output to a different number) with an autogenerated version number that is also mark AS something like 4.20.2323232.devbuild-securityrisk. I truly don't want unsigned nugets flying around that would allow people to tamper / build them and will allow them to put malicious code, I was already concerned about those unity builds.. Please let me know what you are trying to contribute!

[juanfranblanco]

BTW, remember the Nethereum full package, it is already in Nethereum.FX for most of the packages, there are many users getting confused with this, again a security issue, people don't read the readme and realise that is a CI dev build, so if you can transfer the ownsership will be great and I do something about that.. although that is good for anyone not using the other extended libraries.

[knocte]

Hola!!, this is going to need a different nuget build (output to a different number)

This PR is not related to nuget package generation, it's about just dotnet build (because we're talking about GitHubCI here, not AzureDevops).

it is already in Nethereum.FX for most of the packages,

Ah cool, will try that package and if it works for us, then we can rename it to just 'Nethereum'.

[juanfranblanco]

@knocte

this workflow does the nuget build this is what I meant

[knocte]

this workflow does the nuget build this is what I meant

But nuget.bat is not pushing a nuget package to nuget.org.

[juanfranblanco]

Yes but either way it is not a "valid" build it is a dev build.. I have changed it now .. I am seeing dlls flying around, imagine nugets too (people will get hacked..). It looks like this now.. also easier versioning with the suffix 317877f
Edit: what do you think?

[juanfranblanco]

Ahhh I actually got you now, you just want to trigger the nuget build as a way of testing the build works.. as opposed to publish it or keep a copy of it in a branch (which is the step it was missing and was going to add... :) )

[juanfranblanco]

Note on this.. if ever wanted to commit the nugets to the devbuild folder use "skip ci" in the commit message, and commit the changes after build