<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=538262) </details> <!--IssueSummary end--> # Context As a part of https://gitlab.com/groups/gitlab-org/-/epics/17598, the Settings \> Repository \> Protected branches is being removed as duplicate functionality of Branch rules. A CI/CD warning banner was introduced to the Protected branches section in https://gitlab.com/gitlab-org/gitlab/-/issues/417284#note_1485088777. This banner may have been created without UX oversight.  # Design questions * Does this information need to exist on Branch rules? * How should it best be displayed? * What should the visual hierarchy of the alert be? * The alert is currently a warning banner, but does the information warrant that level of urgency from users? * Should the alert show up in all scenarios? * If a user has their settings configured so that nobody can push to any branches, the alert information may not be relevant. * Should the alert be dismissible?