mkdkr VS NUKE

My main problem is running the job/step locally and not wait to CI steps to validate some change.

My solution is: https://github.com/rosineygp/mkdkr

I can write somethings like this:

```Makefile

I just put it in a small solution that I can run in a lot of CI platforms.

https://github.com/rosineygp/mkdkr

in another words: https://xkcd.com/927/

Is it similar to Nuke?

Another thing I could recommend is to use something like Nuke build system to automate more complex tasks that aren't good fit for csproj using C# code (for example - publishing and zipping self-contained release of some service for specific platform using current date and time or commit hash as version number).

testcontainers and https://github.com/dotnet/Docker.DotNet are on my to-do list to try out, but just like with something like https://nuke.build/ i can't see the value other than that the config would be c# instead of some flavour of yaml.

We started using https://nuke.build/. Early days so can’t comment too much but it seems good so far.

I think you're giving a really bad example of what consumers should expect from open-source projects. This year I reworked the whole website, released several versions, did a huge chunk of development, and spoke at 5 events (with travel). This is the first significant gap in almost 6 years of continuous development. Maybe it's hard to imagine, but also maintainers sometimes face severe issues in their life. Comments like this don't make it any better.

Posting this here because I think only .NET people use Nuke (https://nuke.build/) to manage their build.