Closed Piedone closed 1 year ago
@Piedone That's really useful, and I can see there are other workflows that would be good to have as well. Currently we're using Azure DevOps to build/publish the modules. If we decide to switch to GitHub actions then I'd definitely be interested in using some of the workflows in the repo you've linked.
Ah, it didn't register for me that it's actually an Azure DevOps pipeline, I've just noticed the YAML. OK, then.
Seeing https://github.com/EtchUK/Etch.OrchardCore.ContentPermissions/commit/74144c1ca86aec95ce908f42b80bcdcca3e63202. I suggest checking out this reusable workflow we've created for NuGet publishing: https://github.com/Lombiq/GitHub-Actions/blob/dev/Docs/Workflows.md#nuget-publish-workflow Apart from pushing the package to NuGet, it also manages the version number in the Manifest and assembly, adds Source Link, creates and pushes a symbols package, and create a release on GitHub.