Same here. It'll probably be easier if I ever get around to leveraging conventional commits to generate change logs / release notes but until then it's just a habit without much benefit.

You can also include/exclude files/folders with glob patterns too IIRC so for example if you update content under an examples folder and don't want that to increase your version, you can configure that.

If you define the base version in your version.json as 1.0 then commits will increase patch num. If you later create a v1.1.0 tag, that can automatically trigger new commits after that tag to reset and increment from 1.1. I haven't used all the bells and whistles available but it's pretty flexible.

Oh, and this screenshot is from a project I'm working on with my team at work and the project was scaffolded by a fellow principle engineer. It happens, and it isn't just a beginner developer thing. No shade to anyone – just something to consider to make everyone's jobs easier.

When making changes to a project, it becomes a frustrating and repetitive time waster to remember to stage just the changes you made and to ignore changes to all those artifacts. And depending on how the project is organized, you risk accidentally discarding actual changes while preparing to commit.

It takes a little work to update your build script to pull that version from nbgv and stuff it into your manifest and changelog as I haven't seen a pwsh project scaffold do this by default but I inherited the habit from some C# projects at work and just love not worrying about versions anymore.

Nerdbank.GitVersioning it's a neat dotnet tool for auto-generating version numbers based on your git commit height. So if your version.json says your initial major/minor is 1.0 then your next commit is automatically version 1.0.1, and each commit increments your version automatically.

All that said, it's relatively easy to automate creation of tags and releases and at a superficial level to me a GitHub repo seems more complete when I see releases there. Feels like the project is more alive and like the devs care.

I have used v* tags as a trigger to publish to the gallery but I like to use nbgv to generate versions for me based on git commit height and it's a minor hassle to check the version at a given commit, tag it and push the tag.

I have, but I don't usually create releases for module versions since my releases are published to PSGallery and I haven't encountered anyone who makes it a habit to download and install pwsh modules from GH release pages.

No idea but I wonder what it would look like to group a snapshot of posts by emoji use and use ollama or your service of choice to extract some common topics/themes?

This reminded me of a ThioJoe video from a couple years ago related to the .zip TLD!

Thanks! Happy to finally make it public - especially since I'll be able to use it as an example during my telemetry session at #PSHSummit next year 📈

Yep. They've pretty much forsaken Windows at this point with PowerShell 7.5. Well, not really, but many of the pwsh devs are on macs and one of the big pushes for PowerShell in the last 10+ years has been enabling cloudscale infra and the cloud runs on Linux. You'll find quirks but you might like it

Pwsh is a bit like Python in that it is a REPL like Python, but a shell at the same time. Want to run a native command or python or whatever, just do it - no ceremony necessary. Also will happily run pwsh scripts. It, combined with the PSReadLine module make it easy to find your way around too.

Thanks! I sent an email to Rep challenger Peter Larson to say I was rooting for him, and got a nice response back. I also saw the four dems in The Dalles a couple weeks ago and they are all great! I would be happy to be represented by ant one of them. If nothing else I hope Cliff rethinks things.

Maybe steganography methods could be used to embed authenticity data into the media?

It would be easy to remove this data, but could be made very difficult to present something as being recorded by a specific person or organization if the recipient requires "signed" media.

On mac and linux I usually use "#!/bin/env pwsh". For the uninitiated "powershell" is for Windows PowerShell <= 5.1 while "pwsh" is for the cross-platform powershell (versions > 6)