If I understand your issue correctly, here is an article with a terrific
graphic that shows how various feature modules can be brought into a
product release. Your widespread files, with their own enhancement paths,
are the feature lines in the graphic.
On Friday, April 4, 2014 1:09:08 PM UTC-4, Thomas Beardshear wrote:
> Anyone have any suggestions for using git for multiple projects?
> The concept of git seems clear for one large project, but when your
> applets are in multiple locations (departments vs server functions vs
> cloud-based vendor integrations), it gets a little vague especially for
> people that use it periodically.
> I used to simply ZIP each folder(collection of scripts/applets/programs),
> move the ZIP file to a backup folder, then modify a file. Works great but
> I'm zipping ALL files instead of just the ones that changed.
> This works great for multiple projects, multiple storage locations, etc...
> Now it's time to put it all together:
> Multiple Storage Locations:
> Here is a typical setup (with a SUBSET of folders and projects)
> Notice the UNRELATED folders. When I use GIT, it reports that they are
> unmonitored - when is perfectly fine that they are, but disturbing that
> they are listed as unmonitored, not to mention screen-cluttery...
> What "concepts" in git should be used to manage the different
> server/department project folders/subfolders?
> Branches are designed (as I understand it) to test code and maintain
> versions. But these are unrelated PROJECTS.
> Should I use a different GIT file for each server/department/vendor?
> Is there another "structure management" feature that I'm missing?
> (no third yada is necessary here...)
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.