4

I have two apps/projects - one for customers and one for workers. Both projects have the same back-end API related code, the same business-level objects, the same custom GUI controls and some functionality. I want to replace the identical code with the shared one. For example to move this code to a separate repo.

Since both projects are under development everything (including shared code) will be changed very often. Shared code will be usually updated as a part of one of these two projects.

What is the best way to share the code between two projects if I need an easy way to frequently update it?

My ideal use case will be the following:

  1. I change the customer project (customer and shared code).
  2. I commit and push new changes to the customer repo and to the shared code repo.
  3. I open worker project, do pull for the shared code and then update worker code if it needs to reflect shared code changes.

P.S. Qestions Differences between git submodule and subtree and GIT Nested repositories: Composer vs. SubModules vs. Subtree vs.? have very good answers but it is still not clear what should I choose if I need an easy way to frequently update shared code.

Community
  • 1
  • 1
Avt
  • 16,927
  • 4
  • 52
  • 72

1 Answers1

2

I would use a git submodule personally, it's a very good link to a shared codebase that is itself a git repository that can be managed separately without being tracked in your other projects.

You can use git submodule foreach git pull origin master on both the client and worker side to pull in changes when the shared library is updated.

Ryan Collins
  • 679
  • 1
  • 6
  • 13