Structuring related components in git

by

The criteria for combining different set of files in one “component” (here one Git repo) is their respective development lifecycle (the way they evolve in term of labelling and branching):

  • can you make evolution on php or java module without having to make any modifications to other modules (like the obj c ones)?
  • can you isolate in a branch some evolutions/fixes which are only made for one of those modules and not the others?
  • can you reuse a specific version of one of those modules in several projects?

If yes, a component-based approach is best (i.e. one git repo per module), as opposed to one repo with everything in it (system approach).
See for instance “Component based web project directory layout with git and symlinks“.

A component represent a “coherent set of files” and is best managed in its own Git repo.

More Related Contents:

  1. How do I resolve merge conflicts in a Git repository?
  2. How can I add a blank directory to a Git repository?
  3. How do I list all of the files in a commit?
  4. Modified files in a git branch are spilling over into another branch
  5. Track all remote git branches as local branches
  6. Git keeps prompting me for a password
  7. Two git repositories in one directory?
  8. Create a submodule repository from a folder and keep its git commit history
  9. Remove file from git repository (history)
  10. How to commit my current changes to a different branch in Git [duplicate]
  11. git log and show on a bare repo
  12. How does CocoaPods work
  13. git fetch, FETCH_HEAD and origin/master
  14. Using Git diff to detect code movement + How to use diff options
  15. Commit only part of a file’s changes in Git
  16. How do I convert a bare git repository into a normal one (in-place)?
  17. Git remote branch deleted, but still it appears in ‘branch -a’
  18. git pull keeping local changes
  19. push –force-with-lease by default
  20. Remove commit for good
  21. Move file and directory into a sub-directory along with commit history
  22. ‘receive-pack’: service not enabled for ‘./.git’
  23. git clone fails with “index-pack” failed?
  24. Git: How to create patches for a merge?
  25. Pushing to github after a shallow clone
  26. How to ‘git pull’ into a branch that is not the current one?
  27. Amend a commit that wasn’t the previous commit [duplicate]
  28. GitHub – prevent collaborators from using push -f
  29. Bower install using only https?
  30. Git hangs while writing objects

Leave a Comment