The unmerged backports section lists potential missing backports, but we're finding this to not be as relevant in certain situations.
For package.json, the older branch is in maintenance mode and the suggested PR's will not be backported
For CODEOWNERS, the file is deleted and the suggestions will not resolve the conflict.
When this happens it can be confusing for the author on whether to wait for the missing backport or to proceed without it.
Would it be possible to disable the possible missing backports section, leaving only the action status?
The unmerged backports section lists potential missing backports, but we're finding this to not be as relevant in certain situations.
For
package.json
, the older branch is in maintenance mode and the suggested PR's will not be backported ForCODEOWNERS
, the file is deleted and the suggestions will not resolve the conflict.When this happens it can be confusing for the author on whether to wait for the missing backport or to proceed without it.
Would it be possible to disable the possible missing backports section, leaving only the action status?