Currently, if we reach a "conflicting" case in a codeflow subscription when the source repo is adding dependency Foo and the target is removing it (or vice versa) we throw an exception, and never push a commit or anything like that. This can lead to a PR not being created at all, which is undesirable behavior.
Goal
- Don't throw an exception in this situation, except what the target branch has
- Ideally put a comment in the PR so the PR reviewers are aware that this happened
Currently, if we reach a "conflicting" case in a codeflow subscription when the source repo is adding dependency
Fooand the target is removing it (or vice versa) we throw an exception, and never push a commit or anything like that. This can lead to a PR not being created at all, which is undesirable behavior.Goal