When backporting a configuration change that depends on a non-production change in a different repo, [[ https://gitlab.wikimedia.org/repos/releng/scap/-/blob/1ad6b0f670ed03da4a9d86f3f271bbcbd935063c/scap/plugins/backport.py#L738 | we prompt the user for confirmation ]]. ~~This behavior is incorrect when the dependency has already been merged, in which case the dependency should simply be ignored.~~ The dependency being merged is not enough to ignore it -- even if merged there's still a chance that the code didn't make its way to production. A more clear, more informative message should be shown to the user instead so they can make a decision on whether to continue the backport.
~~[[ https://gitlab.wikimedia.org/repos/releng/scap/-/blob/1ad6b0f670ed03da4a9d86f3f271bbcbd935063c/scap/plugins/backport.py#L685 | A recently added warning message ]]~~ (the message was moved to a different location in code, but was already there) shown with the prompt surfaced the bug and confused a backporter: P58805