Check out F# "units of measure" ;)

hahaha :D

maybe it's worth adding that info to the blog post :)

thanks Jared and team, keep up the great work.

it is documented as recommended here fwiw: https://docs.github.com/en/actions/security-for-github-actio...

And the syntax to do that is to use `foo/bar@commitshagoeshere` as in

    - uses: RafaelGSS/bad-action@e20fd1d81b3f403df56f5f06e2aa9653a6a60763 # v1.0.1

(example from https://blog.rafaelgss.dev/why-you-should-pin-actions-by-com...)

This. Using tags is acceptable only for official GitHub actions, anything else should be pinned.

but this comment is gold :D

> Sounds like deleting a VM in Azure is as tedious as trying to manage resources in a complex role-playing game—one wrong step, and you’re stuck dealing with frustrating dependencies! If you’re tired of that kind of hassle, maybe it’s time to switch things up with Download SpinRP. Instead of deleting VMs in the right order, you can dive into an immersive world where strategy and excitement go hand in hand. Why deal with a “big fat pink error” when you could be making big moves in SpinRP instead?

you could call it a "Registry"... ;)

I've worked on maintaining internal dev tooling for some small companies for a while now, and it's a real PITA to write a robust installation script for bootstrapping a new laptop running an arbitrary shell on linux or macOS into a working environment. Way more work than it feels like it should be.

At this point I've pretty much given in and decided that a containerized dev environment is probably the better solution, but on principle it feels so unsatisfying to have to resort to this :(

(I know someone is going to mention Nix/Guix ;) but that feels like a giant rabbit hole)

I worked at Seagate in the early 2010s, and they made pretty intensive use of Lotus Notes across the company—-it was pretty dang cool to see how sophisticated/useful the internal applications were that non-“developers” created!

What if you have a microservice system with a repo-per-service setup, where to add functionality to a FE site you would have to edit code in three or four specific repos (FE site repo + backend service repo + API-client npm package repo + API gateway repo) out of hundreds of total repos?

Codebuff works on a local directory level, so it technically doesn't have to be a monorepo (though full disclaimer: our codebase is a monorepo and that's where we use it most). Most important thing is to make sure you have the projects in the same root directory so you can access them together. I've used it in a setup with two different repos in the same folder. That said, it might warn you that there's not .git folder at the root level when this happens.

This does seem to be suited to monorepo.

Yes, unfortunately, Codebuff will only read files within one directory (and sub-directories).

If you have multiple repos, you could create a directory that contains them all, and that should work pretty well!

how about just having rustup bundle zig as part of its tooling… It would make getting Rust going on Windows ten times easier, among a bunch of other benefits.