@justine You should definitively look into #git #submodules.
I did what you're doing a while back. And having a repo of repos instead of a directory of repos is a blessing.
Need to update : `git submodule update`.
No loop, no bash, no "involved" logic, just use what's already there instead of reinventing the wheel.
@mms

My new article on Hugo modules vs. Git submodules is LIVE! 🚀 Learn how to streamline your website management. Read now: https://drmo.site/fnJbML #Hugo #Git #Submodules

Your main #quarto website repo shouldn't be a storage unit for every plot you've ever made 📦

#git #submodules: Give your figures their own space, keep your repo fast

https://blog.thecoatlessprofessor.com/programming/quarto/stop-bloating-your-main-quarto-website-repository-with-generated-figure-files/

People please learn to use #git #submodules for your dependencies. This is the only way that allows you to vendor the exact commit/version into your app while also allowing you to easily update them regardless of where it is checked out. Especially for CI/CD this allows e.g. access token to just magically work. Regardless of how deeply nested they are.

(also don't split a monolith across multiple repositories using it, submodules *only* excel for managing standalone dependencies)

So what's the smoothest way these days to integrate localisation repositories into your git repo?

As a background: our localisation needs to live in a separate git repo that is monitored and also updated with new translations by pootle (a translation tool) but we also want to be able to pull out the generated PO files as well as push local updates (and new texts) from within the containing project repo the localisations belong to. So merges / rebates are kinda required.

Git submodules are the worst case here as you can't really commit / push local updates to the translations back to the localisation repo without making a separate checkout, doing your changes there, then pushing to your remote and finally updating the reference for your local submodule and pulling again.

Git subtrees sounded like a good idea but they way they're implemented makes them nasty to use as well.. they tend to break if you work with pull --rebase in the containing repo and merge conflicts in the sub tree can't be resolved with a sub tree-rebase either.

In the past I used to have the localisation as a full git checkout in a sub directory of the containing project and maintained it using a few CMake scripts but I had hoped there's be something smoother by now.

#git #submodules #subtree #localisation #i18 #workflows #question #SofwareDevelopment #boostswelcome

A new post on my blog:

Nested repos

I've once again been thinking about git submodules and how I might be able to use them when making games. My requirement is to have my open source game, but potentially use commercial assets inside without exposing those assets in a public git repo.

I also took a side quest to look at Mercurial, since the "best" source control systems for game development are stupidly expensive. Mercur

https://taffer.ca/nested-repos/

#GameDev #git #submodules

I wrote a blog post on why I use #git #submodules despite the fact that they're awful :)

As I say in the article I welcome ideas on how to do this differently. My implentation isn't perfect but it does what I need for now!

https://www.feoh.org/posts/git-submodules-are-awful-but-occasionally-necessary

@ricardoramos @Whar I forgot to mention the obsidian-git plugin - it provides seamless #git integration for #obsidian , including git #submodules if you use them.

Depending on how sensitive my vault is, I use GitHub, or a #cryfs #encrypted file based repository on #cloudstorage such as Dropbox.

#nix flakes and #submodules—a new source of pain. ffs.

Somewhere in the world @jacobsee has probably felt a disturbance in the force and is probably laughing due to numerous occasions of me having a meltdown over projects that have used #submodules.

Git Submodules

Eine eher vernachlässigte Git Funktion sind die Submodules. Mit diesen kann man in ein Git-Repository andere Git-Repositorys einbinden. Dies ist vor allem Praktisch, wenn ein Teil des Großen und Ganzen in Testing laufen soll und der Hauptteil im Stable.Dies hilft auch im Upgrade Prozess oder wenn man immer wieder dieselben Repositorys in

https://openmagazin.de/2021/06/git-submodules/

#Einsteiger #Software #Tutorial #coding #entwicklung #git #programmieren #submodules

Bei einem public #git repository bei welchem ich #submodules benutze um den code anderer (freie #lizenzen) zu nutzen, muss ich diesen doch sicher in der readme oder so angeben oder?