Looking at the issues on validation that we had recently, I think a new workflow for the PR is required. Here my proposal:

• PR on submodules trigger the creation of a PR on framework and the submodule hash is updated accordingly in framework. If the PR of the same branch already exist in framework with the same branch name it just commit the changes on the submodule hash. For instance, something similar is done at https://github.com/releasehub-com/github-action-create-pr-parent-submodule
• PR can only be merged from framework and it will automatically trigger the submodule, this can address this issue Automatize submodule PR if framework name matches with submodules  #250 since some work has been done here New workflow frameworkPR for automatic submodule PR merging #259
• The pipeline validation will only run at framework so we avoid to trigger the pipeline when a PR is performed in e.g. different submodules and in framework.

@jgalan and @lobis let me know what do you think since this is a lot of work.