3 ms·
And then you always forget what you need to do after you didn't do it for months. I have a blog project (written with pelican) where I submodule the whole pelic
by maweki 6y ago
And then you always forget what you need to do after you didn't do it for months. I have a blog project (written with pelican) where I submodule the whole pelican-plugins project which is, basically, again a compendium of submodules.
Now when running Python creates pycache-folders in the submodules and other stuff in the directories sometimes changes a bit while running.
When it comes to updating the plugins-submodule, I have to go through every sub-submodule and git clean it and reset it so that I can pin a new version for the submodule, and then update all sub-submodules. Mind you, I have not found it easier to delete the whole submodule-tree and re-initialise it.
- angrais 6y agoWouldn't this be resolved by a good README.md?
- maweki 6y agoOf course, the correct way would be to write down all the steps, operationalise them, and then implements parts and then the whole as a shell script. The question I would ask is, whether this should be necessary to pin the version of some project dependency? That's basically all we're talking about here.
- Pxtl 6y agoCode is the best documentation. update-submodules-latest.sh (well, PS1 for my team, we're a .net shop) to move to latest along their branch and stage the submodule change