Recently we faced some issues when a submodule PR is merged while the required PR in framework is not merged. This issue can be addressed by automatizing the PR in framework when a branch of the same name is present in any submodule. This in principle can be done with a dependantbot https://docs.github.com/en/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions. We need the following requirements:
- A PR in
framework should trigger any submodule PR with a matching branch name.
- As soon as the PR is merged in
framework the different submodule PR should be also merged.
- A stand-alone development in any submodule should not trigger any action in
framework
- A PR inside a submodule which matches any
framework branch should not be allowed.
Recently we faced some issues when a submodule PR is merged while the required PR in
frameworkis not merged. This issue can be addressed by automatizing the PR inframeworkwhen a branch of the same name is present in any submodule. This in principle can be done with adependantbothttps://docs.github.com/en/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions. We need the following requirements:frameworkshould trigger any submodule PR with a matching branch name.frameworkthe different submodule PR should be also merged.frameworkframeworkbranch should not be allowed.