We have a lot of branches (because we have a single repo) at any one time. As is common, feature branches frequently get merged into master as code is released.
I’m seeking a way to have some form of automatic analysis performed so that whenever new commits get merged into master we can see which other branches must be updated.
Clearly if a file in a commit merged to master also appears in a commit on some other branch then that branch must be updated (have master merged in and the app rebuilt).
But we must also merge and rebuild (from master into some branch) if there is a folder in common, not just a file.
The folder may represent an app and we might merge some new stuff to master including a change to ProjectX/FileM.
Then if we have some other branch that touches a file ProjectX/FileK then we need to know and may want to merge master into the branch and rebuild the app.
The goal here is to try to automatically discover if merges to branches (often master but not exclusivley) require an app rebuild on some other branch, this is done “manually” now by people “knowing” what’s going on.
Of course Git knows nothing about projects, solutions (we’re primarily Microsoft based here) but a folder based analysis might be sufficient, at least as a first step.
So is there any way to do this currently?