Yup, it already supports WhatIf, but doesn’t list all of the files that would be deleted; it just lists the repos that would be cleaned. I’ve started looking at implementing showing the files today already 🙂

I'll note that the primary use case for this module IS to delete files/directories that are in the .gitignore file. e.g. build artifacts, NuGet packages, node_modules, etc.

I'm going to see if I can make it a bit safer though 👍

Providing that option as a parameter sounds like a great feature request 🙂 Noted ✅

Or are you saying that you have files in your .gitignore that you actually don't want to be deleted? e.g. you don't want to commit your .vscode directory to git, but also don't want it to get deleted?

Is that a question? Or are you saying that it did delete them?

If it detects untracked files in the git repo, it won't clean the repo. In the screenshot, you can see the first line shows the repos that had untracked files, so they weren't cleaned. It is meant to prioritize safety.

When you’re a software engineer but don’t work at the company and they ignore your issue reports for too long 😛

"it’s the best way to guarantee reliability"

I would offer that microservices introduce so many network partitions that they reduce reliability. What they do do is force you to think about failure scenarios and build resilience into your apps. You can do that without using microservices tho

"microservices should be the default for every application"? Yikes. Even small applications? What about applications with only a single dev team?

The answer is definitely "it depends", but I'd hazard a guess saying microservices are appropriate for less than 5% of applications.

Write-CaptainsLog -StarDate (Get-Date) -Message $message
---
Set-Lifespan -Long
Grant-Lifestyle -Prosperous

I believe it's only available to MVPs with an award in the DevOps technology area.

I posted a link to this msg in the MVP GitHub Slack workspace, so hopefully someone reaches out shortly 🙂

Also, did you specify a restricting glob pattern perhaps?

IIRC there’s an API key permission both for publishing new modules and publishing new versions of modules. Did you check both permissions?