[Frontend] Allow filtering compliance violations by branch
Problem to solve
Previous description
The compliance now shows individual merge request violations for all branches. This means it show violations across protected branches, such as `main`, but also for one-off branches that may be used for experiments or for branches that don't need to be monitored. This makes it challenging for Cameron to find violations for the only branches they care about.In spirit of iteration it was decided in #358412 (comment 1347435840) to allow only exact match filters by branch, so this issue was updated to track this effort
Proposed solution
Once the filter component and backend is built integrate it.
Implementation plan
frontend weight
- Use the
targetBranch
param in the GraphQL query introduced via MR !117240 (merged). - Create a search bar as per the design in this comment.
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.
Edited by Illya Klymov