4 ms·
I've read the README (and I've also used git-subtree in the past), but it's still a bit unclear to me how this is intended to be used. What's the typical flow?
by judofyr 7y ago
I've read the README (and I've also used git-subtree in the past), but it's still a bit unclear to me how this is intended to be used. What's the typical flow?
- When should I run `subtrac update`? Only once? After every change in submodules?
- What happens if I go into a submodule folder and change a file? Should I commit inside that repository and push upstream? How is that propagated to the the parent repo?
- Does this allow me to make a change to the submodule and not push upstream, but instead "commit" it to the parent repo only?
- What is the master.trac branch? Should users checkout this branch, or is it just there for referencing data?
- apenwarr 7y ago[author here] Hey sorry, git-subtrac is new and I didn't know what to put in the docs. To quickly answer your questions: 1. You should run it every time you make a change in a submodule. 2. You commit inside the subrepo, then run 'git subtrac update' in the parent repo. You don't need to push the subrepo anymore unless you want to (eg. because you're submitting upstream). You do need to push the new .trac branch in the parent repo somewhere - probably to the upstream parent repo. 3. Yes, exactly right. 4. It exists just to create references to all the objects in all the submodules. If you push it somewhere, then you can fetch all your submodules from there. The most common place to put it is in the parent repo, so that cloning that repo gives your users a clone of all the dependent submodules too. Hope this helps!