You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 text was updated successfully, but these errors were encountered:
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 backportedFor
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 text was updated successfully, but these errors were encountered: