Git workflow for 2 separate projects sharing similar code -
i have 2 projects each need similar functionality ( custom wordpress plugin ). 2 substantially different in implementation fundamentally same thing underneath hood.
i working on both of these projects concurrently, ( , on own not part of team ).
i don't know git enough know there workflow use here don't have develop projects separately, or maybe should developing them separately, don't know.
the way imagine would fork first project , have 2 separate repos, fine want able bring in changes project #1 project #2 later ( after more code has been added after fork ) ... , might want to have same thing going on other direction ( p2 p1 ) .... can me make sense of should aiming here.
it depends on how 2 projects isolated/co-implemented, can git submodules.
it adds complexity of managing third branch/repository, architecturally enforces hard division between , isn't shared between 2 projects having both include third shared git submodule.
Comments
Post a Comment