Home/ Questions/Q 7705595
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-31T23:54:08+00:00

I have directory structure like so: |– ROOT |– Project1 | |– application |

  • 0

I have directory structure like so:

|-- ROOT
    |-- Project1
    |   |-- application
    |   |-- img
    |   |-- js
    |   |-- css
    |   `-- system
    |
    |-- Project2
    |   |-- application
    |   |-- img
    |   |-- js
    |   |-- css
    |   `-- system
    |-- Project3
    ....

Root folder contains total of x projects: “Project1”, “Project2”, “Project3” and so on.

Now i’d like to use git on “system”, “css” and “js”.
These folders should be identical for each project.
So how can sync all projects with git?

I’m guessing to create a “Master Project” and push new modifications to there and pull new version to all other projects. But that’s pain in the a**..

What i’d like is to run some command/batch file to sync all at once.
Eg if i have 6 projects and i modify something in project 1, how can i get this modification to all projects fast(instead of pushing Project1 to “Master” and pulling it 5 times)?

Is it possible?

Just for a record i’m working on a Windows machine.

Previous question: Git between multiple projects

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You still probably want to use a submodule. See this page in the git book.

    Using submodules makes handling the types of changes that you are talking about fairly straightforward. See the second half of this answer which summarizes the process well.

    I’ve modified my previous answer as I can see that this could be a bit of a pain for multiple projects if you need to keep them all in step as updating all the submodule commit references in the main project will take some time. As per the previous answer I suggest that you script this process if that is what you want to do.

    It does have an advantage once the projects mature however as in my experience it often happens that all projects cannot be updated at once. Sometimes one project still requires an older version for a period of time. In this case you can just to update the required projects to reference the new commit in the submodule and then upgrade the others later when you have time.

    • 0