Databases
StackOverflow2013
Postsdbo
POGit workflow multiple repositories and rebasing(?)
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGit workflow multiple repositories and rebasing(?)
    text
    copied!<p>Hey guys I've been wondering if this could be feasible? I've been pondering over it for hours and I can't get my head wrapped around it!</p> <p>Say I have X clients interested in a e-commerce/cms system ( basically whatever ), in my perfect world I would like to have this situation ( If you think I'm crazy convince me otherwise please! I'm open for different suggestions ):</p> <p><strong>Software Repository ( A )</strong> <em>being the e-commerce system or cms</em>, at it's latest version. Which would be periodically updated depending on vendor release cyclces. ( Yes I'm aware it might not be the best idea to version the software dependency in here, but I'm interested if this 3 layer "cake" is actually do-able ).</p> <p><strong>Design Repository ( B )</strong>, multiple of these containing a certain base style to start off from. Tied to the software vendor's approach.</p> <p><strong>Client Repository ( C )</strong>, this would be an initial checkout of the master of A, containing a certain style of design, say B-2. And would be updated with specific client features, styles etc.</p> <p>Now let's say we've made a client happy with our project and I would like to make them even happier keeping their CMS / e-commerce solution safe by providing regular updates, is there any (easy) way to do this sort of fashion of work:</p> <ol> <li>Update the software repository with a new version of the e-commerce / cms software</li> <li>Commit these changes</li> <li>Pull these changes into the corresponding design ( and of course spawning multiple, if necessary ). And provide an update of new features in a design or what-so-ever.</li> <li>Commit these changes into the specific design repository.</li> <li>Now we start pulling our client repositories and update these with the previous changes, where-after we are able to deploy.</li> </ol> <p>The only way I've seemed to figure this out is based on git-rebasing within a single repository, between several branches, however this doesn't seem like the ideal solution to me.</p> <p><strong>Am I a lunatic? Or do I need a smack with trout and get an easy solution?</strong></p> <p>Thanks for taking the time to read / respond!</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload