For code? Use the context7 mcp.

Great tool! Prior me is sad this didn’t exist!

I’d be fine with a live summary status updating showing # available and # taken. Hitting ctrl+c resulting in printing the lists as above.

Also perhaps a —timeout flag, or similar as I may only want to wait 5 minutes / length of time it takes to steep tea for answers.

I know far too much about python packaging while only knowing a little about it.

I agree it’s hell. But I’ve not found many comprehensive packaging solutions that aren’t gnarly in some way.

IMHO the Python Packaging community have done an excellent job of producing tools to make packaging easy for folks, especially if you’re using GitHub actions. Check out: https://github.com/pypa/cibuildwheel

Pypa have an extensive list of GitHub actions for various use cases.

I think most of us end up in the “pure hell” because we read the docs on how to build a package instead of using the tools the experts created to hide the chaos. A bit like building a deb by hand is a lot harder than using the tools which do it for you.

Came here to say this, and to recommend: https://github.com/appleboy/ssh-action

It’s slow and arduous work to inject at the right point and find out what went wrong. But it’s miles better than act. act is a noble idea, and I hope it can meet its target, but it falls short currently.

ssh-action gets you on the host, and lets you quickly establish what is happening and implement fixes. It’s top notch!

(I’m unaffiliated, just a big fan of ssh-action).