|7eter l-|. l3oling 🧰Building things that make my life as a maintainer 10x easier is... awesome. rake task "ci:act" that ships with kettle-dev gem creates an interactive menu with latest CI status for each workflow (less a few exclusions), and allows picking one to run locally via nektos/act
I use this to check the status after a push, so I don't need to switch back to a browser, and also when a workflow fails, I'll run it locally to see what's going on.
ANN: kettle-dev v1.1.0, which removes *all* runtime dependencies, and has a script that will bootstrap itself into a gem. It's a template, and makes a lot of changes, to align a gem to how I would want it. You won't want yours the same way, but forks are welcome, and I'm happy to generalize it to be less centered on my peculiarities (e.g. my badge fetish).
More tools added to kettle-dev v1.1.3:
- kettle-dvcs will setup locally federated git remotes under a multi-push "all"
- kettle-dvcs --status will help you remember at a glance if there is remote work that needs to be upstreamed
- simply run git push all to push changes everywhere
Bradley Schaefer@galtzo this is your tool for managing multiple repos across multiple hosts?
It seems like there’s a lot going on in this tool, I wish for better tools for managing many apps/repos in my workflow
@galtzo re-skimming, maybe it’s a tool for managing a single repo across multiple hosts. Still useful when applied across many repos, I reckon
@soulcutter kettle-dev is my mega gem that has all of my tools for maintaining gems. One of the things I try to do with each gem is DVCS, where the D is Distributed, as in Federated.
I wrote about it here:
https://railsbling.com/posts/dvcs/put_the_d_in_dvcs/
I wrote about it here:
https://railsbling.com/posts/dvcs/put_the_d_in_dvcs/
@soulcutter A multi-hosted repo is a small, and optional, part of the tools.
I'm actually releasing a gem with it right now.
I'm actually releasing a gem with it right now.
@soulcutter https://ruby.social/@galtzo/115134860821957831
And, yes, it is my expectation that this tool will bring maintenance of my many gems back into the realm of possibility. There was no way I would ever catch up if I had to run all the commands manually. This tool now does dozens of checks, and hundreds of file updates, automated commits, automated workflow readme updates whever there is a new backer, etc. A huge list of automations.
|7eter l-|. l3oling 🧰 (@[email protected])
Attached: 2 images :ruby: Most of the CLI-level tools kettle-dev ships with. https://github.com/kettle-rb/kettle-dev/ #Ruby #FLOSS #DevTools
@soulcutter
> It seems like there’s a lot going on in this tool,
Also, yes. I'm mostly just encoding my patterns and operationalizing them. I have a few broad separations already, one gem for testing stuff: kettle-test, one gem for code coverage stuff: kettle-soup-cover, and one gem for dev stuff: kettle-dev. I expect more subdivisions will be forthcoming. kettle-dev is already a fairly large codebase for what it is @ almost 3k lines (not including extensive tests).