I have created a main repo “infrastructure as code” and 5 sub modules:
infrastructure as code
Now that we have our core code in these directories, we have started with our feature branches on all the repos and require a pull request to make any changes on any of the code in these directories. We started out with “Require a minimum number of reviewers” 1, and “Allow users to approve their own changes” to start with. We also have as optional “Check for linked work items” and required “Check of comment resolution.”
When I set this up, I set the same requirements for the main repo, “infrastructure as code”. This is the question. It looks like it tracks changes to the sub repos and requires a push to update what was done in the sub repo. Which I can’t do because of the restrictions not allowing git push. Does this mean I need to create a branch with the main “infrastructure as code” every time I create a branch for a sub repo and update it after and do a second pull request there. Or, do I need to take the restrictions off the main repo, so the update push can be done as needed? Or do I just put the restrictions on the main only and not the sub repos, or some other option I have not yet considered?