Yep trust was always the issue here really. Don’t blame Jannis at all for being super careful about that.

A great looking framework for building an interactive development experience on top of the already awesome Pydantic AI.

I end up needing to write a manual migration maybe once every other year in real world use.

I actually built the last thing last weekend weirdly enough.

gg watch action

Finds the most recent or currently running action for the branch you have checked out. Among other things.

https://github.com/frankwiles/gg

Oh this is excellent. This is everything I wanted the `gh` cli to be, thanks.

edit: Just a quick note, the `gg` and `gg tui` commands for me don't show any repos at all, the current context stuff all works perfectly though.

Ah sorry need to make the docs more clear. You need to run ‘gg data refresh’ to populate the local DB first.

Ah, magnificent! Thanks!

Sure thing. Also just made it easier to install with Homebrew since people seem to be liking it.

May also be worth adding mise to the README install options given its growing popularity. I installed globally with `mise use -g ubi:frankwiles/gg@latest`. I've invoked gg so many times over the last day, it's exactly what I needed - thanks again.

It's super common with non-profits. Obviously they would prefer no strings attached but some light strings are usually not a problem for most non-profits.

And they come in a variety of bindingness. I didn’t notice any details in this link which makes me think this is mostly a handshake deal, but it wouldn’t be at all unusual for there to be some auditing mechanisms on a quarterly/yearly cycle.

For example, Wikimedia just recently claimed that they can’t chase some political project that critics wanted them to because most of their funds are earmarked-for/invested-in specific projects. So it does happen with US-based tech non-profits to at least some extent.

Yeah I think I would have been considered part of the “in” crowd of Perl to some degree and it wasn’t the culture that drove me away and to Python.

It was Django and the people involved with it.

> and the people involved with it.

Culture?

Yeah after the acquisition I’m sure they moved everything to whatever the parent company was using which totally makes sense.

That would have been hard since both of those projects came out after Django, but just an FYI Jinja2 templates are supported and nothing stops you from using SQLAlchemy. Granted you lose a lot of the tight intergration that makes Django great to use.

> That would have been hard since both of those projects came out after Django

Well, yes I didn't mean Django from the start! I mean now.

Hi neighbor! :)