I think you need to relax the ‘no commit to submodule’ constraint. There are two options:
- Commit your submodule changes to a submodule branch. It is your team’s branch and it is where your team put your submodule changes. When somebody clones the super project and updates the submodule they get the content of your team’s branch.
- Clone the submodule repository ‘right next to’ your super project repository and initialize the submodule to point to your clone. Then when you commit changes to the submodule they are committed to your clone. Anybody who clones the super project gets submodule content from your submodule clone.
Otherwise, I don’t see a way to achieve your desire.