#submodules — Public Fediverse posts

Настолько давно не пользовался сабмодулями в Git, что вчера добавив сабмодуль на одной машине уже сегодня на другой сидел и не мог сразу понять а чего проект не собирается-то.

А вы когда последний раз использовали submodules?

#dev #Git #submodules #log #vote #survey

Current state Intelligence Core:

#ETLpipeline : Validated. 5,458 rows ingested in 49s.

#submodules : scraper-base-kit & market-intelligence-connector fully integrated.

#Data Logic: live Z-Score / IQR outlier detection for analysis.

modular architecture self-hosted on #ArchLinux

#BruteForceEngineering #DevAgainstTheMachine #DataScience #Python #Grit #gritlab #AnarchyInTheShell

Current state Intelligence Core:

#ETLpipeline : Validated. 5,458 rows ingested in 49s.

#submodules : scraper-base-kit & market-intelligence-connector fully integrated.

#Data Logic: live Z-Score / IQR outlier detection for analysis.

modular architecture self-hosted on #ArchLinux

#BruteForceEngineering #DevAgainstTheMachine #DataScience #Python #Grit #gritlab #AnarchyInTheShell

Current state Intelligence Core:

#ETLpipeline : Validated. 5,458 rows ingested in 49s.

#submodules : scraper-base-kit & market-intelligence-connector fully integrated.

#Data Logic: live Z-Score / IQR outlier detection for analysis.

modular architecture self-hosted on #ArchLinux

#BruteForceEngineering #DevAgainstTheMachine #DataScience #Python #Grit #gritlab #AnarchyInTheShell

Current state Intelligence Core:

#ETLpipeline : Validated. 5,458 rows ingested in 49s.

#submodules : scraper-base-kit & market-intelligence-connector fully integrated.

#Data Logic: live Z-Score / IQR outlier detection for analysis.

modular architecture self-hosted on #ArchLinux

#BruteForceEngineering #DevAgainstTheMachine #DataScience #Python #Grit #gritlab #AnarchyInTheShell

Not gonna lie, a few years ago when I eared @robinm asking for a built-in plugin manager in #vim / #nvim, I was not convinced.

Why? Because I thought it was already the case. `pack/{opt,start}` has been around for quite a while now and I used #git #submodules to have a portable configuration.

Since then, I've used various plugins manager. They're handy but don't offer much more than the built-in.

And now, back to sugar-coated basics: https://echasnovski.com/blog/2026-03-13-a-guide-to-vim-pack.

I now agree with @robinm.

I use #Git. A feature of Git I leverage heavily is #Worktree. I usually have at least four around at a time. For small tasks, sure, a simple branch and then switch back, but bigger things: a worktree.

Making a worktree is actually annoying for me: not just the upfront decisions about branches and start points and where to put the new directory (and also immediately `cd`ing there: but getting all the #submodules (submodules suck by the way), hooking up `.envrc` if you use #Direnv (and you should be), which should then set up your virtual environment and path and stuff. Clone isn’t quite as bad but has some of the same problems.

I do this so often, I wrote a script. It might be useful to others with this workflow. It’s opinionated, and therefore I could really use some feedback! What did I do right? What did I do that’s only right for me? What is totally missing?

The script is stand-alone, though you do need #UV. (You don’t even need Python! `uv` will transparently get you everything!) Just download this one Python file, and get it on your `$PATH`. If you want the additional `cd` behavior, then add the shell function, too as described in the `README`. Everything is tested. The tests are right there, too.

https://github.com/wolf/dotfiles/blob/main/git/dot-config/git/bin/make-worktree.py

The `README.md` is right next to it.

I **do** see one thing I’m missing: I need to provide a way to automatically copy in your custom stuff. I’ll add that today.