Allow filtering violations by protected branch status
Release notes
Problem to solve
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.
Proposal
Add an option to the compliance report to filter results to only show protected branches, all branches, or to select an individual branch.
- See attached UX design
Important Note: This feature only relates to what data is shown. No changes are proposed to what data is recorded. All merge request violations should still be recorded, regardless of branch status. It is still possible for an unprotected branch to cause issues and it is also possible for an unprotected branch to become protected in the future. If we don't record data for all branches, we would not be able to display those violations later when a user did need to see them.
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.