-
Notifications
You must be signed in to change notification settings - Fork 2.5k
PR #4779 silently reverted #4652 which was already merged to main #4987
Copy link
Copy link
Open
Labels
category/uiUser interface and displayUser interface and displaypriority/P2Medium - Moderately impactful, noticeable problemMedium - Moderately impactful, noticeable problemscope/componentsUI components and widgetsUI components and widgetsstatus/need-informationMore information is needed to resolve this issue.More information is needed to resolve this issue.status/needs-triageIssue needs to be triaged and labeledIssue needs to be triaged and labeledtype/bugSomething isn't working as expectedSomething isn't working as expectedwelcome-pr
Description
Metadata
Metadata
Assignees
Labels
category/uiUser interface and displayUser interface and displaypriority/P2Medium - Moderately impactful, noticeable problemMedium - Moderately impactful, noticeable problemscope/componentsUI components and widgetsUI components and widgetsstatus/need-informationMore information is needed to resolve this issue.More information is needed to resolve this issue.status/needs-triageIssue needs to be triaged and labeledIssue needs to be triaged and labeledtype/bugSomething isn't working as expectedSomething isn't working as expectedwelcome-pr
Type
Fields
Give feedbackNo fields configured for issues without a type.
What happened?
PR #4779 reverted a feature from PR #4652 without any explanation.
What did you expect to happen?
When conflicts occur, they should be resolved within the PR, not by reverting an unrelated feature.
Client information
N/A
Login information
N/A
Anything else we need to know?
N/A